setValue with a different scope overwrites the previous value
Registered by
Martin Preisler
If varconf allowed overriding values without overwriting them, we could easily query default values (with GLOBAL scope) and overridden values (USER, it doesn't exist resort to GLOBAL).
This is a much cleaner solution than getting a snapshot of all GLOBAL variables before loading user config (IMO) and shouldn't be that hard achieve.
getValue(section, name, scope = USER | GLOBAL | INSTANCE) would be the default signature.
If someone called setValue with scope GLOBAL it would of course overwrite the previous GLOBAL variable, I think this won't happen unless done by mistake.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)