We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We have users of an app that need to work with a production version and sometimes test a beta version. How can such a user change channels?
With running the setup for the other channel I guess?
But what about this:
snapx/src/Snap/Core/SnapUpdateManager.cs
Line 266 in 03a5f30
Why hardcode to the current release? Could you provide the channel as an optional parameter with default=current?
The text was updated successfully, but these errors were encountered:
The user would have to download the respective installer for that channel. This feature is on our roadmap.
With running the setup for the other channel I guess? But what about this: snapx/src/Snap/Core/SnapUpdateManager.cs Line 266 in 03a5f30 var snapChannel = _snapApp.GetCurrentChannelOrThrow(); Why hardcode to the current release? Could you provide the channel as an optional parameter with default=current?
I do not remember why it was hardcoded but if I where to guess it was because the feature was not part of the MVP.
Sorry, something went wrong.
No branches or pull requests
We have users of an app that need to work with a production version and sometimes test a beta version. How can such a user change channels?
With running the setup for the other channel I guess?
But what about this:
snapx/src/Snap/Core/SnapUpdateManager.cs
Line 266 in 03a5f30
Why hardcode to the current release? Could you provide the channel as an optional parameter with default=current?
The text was updated successfully, but these errors were encountered: