isXander / isXander/YetAnotherConfigLib
InstantStateManager has invalid assumption
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 155
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
InstantStateManager assumes that it's always synced, since any changes applied to the input are instantly applied to the config. But this does not hold true if the config value changes through different means. In such cases the UI is desynced and, while it does still sometimes display the correct value, brings all sorts of weird behavior.
Why would the config value change?
In my case I have a list of presets, and a lot of options for each. The 'active' preset is selected from a list (like an EnumController). The other options act on the active preset. So when switching presets issue described above happens.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing InstantStateManager and the config update paths involved when switching presets. Reproduce the desynchronization with a preset list and dependent options; done means the UI stays synchronized when the config changes through another controller.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100