isXander / isXander/YetAnotherConfigLib
[Bug] Double settings with a default value of 0.0 cannot be reset
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 155
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
If a double setting has a default value of zero, it will still be detected as changed, even after being reset.
https://github.com/isXander/YetAnotherConfigLib/assets/71229440/5b18bca3-4f4c-450d-9bbc-8e15f6bfeb83
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 reproducing the reported behavior in YetAnotherConfigLib with a double setting whose default is 0.0, then trace the reset and changed-state handling. Done means resetting that setting no longer marks it as changed; verify the behavior with a focused regression test if the existing test structure provides one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100