Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Changing choices configuration requires deleting system
See original GitHub issueCurrently if you change only a choices definition you need to delete the plugin in order for the changes to be picked up. This is less than ideal.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Uninstall or remove apps and programs in Windows
Uninstall from the Settings page Select Start , then select Settings > Apps > Apps & features. Select the app you want to...
Read more >Privacy - Control - Apple
Settings have been carefully designed to put you in control of your data. ... erase the device, or need to change your password...
Read more >Delete your activity - Computer - Google Account Help
At the left, click Data & privacy. Under "History settings," click an activity or history setting you want to auto-delete. Click Auto-delete. Click...
Read more >Changing your Virtual Background image - Zoom Support
Recommended setup with a green screen. Virtual Background with a green screen provides the best virtual background effect and uses less system ......
Read more >What is Amazon S3? - Amazon Simple Storage Service
You can store data with changing or unknown access patterns in S3 ... You can use Object Lock to help meet regulatory requirements...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I would say we want to allow people to change choices without forcing them to release a new version.
The versioning schema that we are enforcing doesn’t actually have any weight behind it. Meaning, someone can change the actual underlying implementation of a plugin without changing the commands/parameters and we currently have no way of knowing that.
If we wanted to go down the path of forcing someone to bump their versions when they change choices, we must come up with a decent way to actually enforce any changes in a plugin resulting in the force of version bump. Which is mostly out of scope. Either way, we would need #20 to be done before I would feel comfortable even enforcing that.
Bottom line: I’d say allow people to change their choices without bumping versions.
@loganasherjones can you weigh in on this?