WayfireWM / WayfireWM/wf-config
[Feature] Option name backwards compatibility
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 24
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
Currently, once an option is in use we are stuck with the name it has.
My proposal is a new tag <also> (or, potentially an attribute on the <option> of the same name
So, theoretically
<option name="new_name" type="int">
<also>old_name older_name</also>
<default>10</default>
<min>1</min>
<max>20</max>
</option>
Which would read from an ini file
[section]
new_name=5
old_name=15
Finding the value 5
and from a different config file
[section]
old_name=15
Finding the value 15
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
The issue does not name any files, tests, or entry points. Start by locating the option and INI parsing implementation, then determine how option names and conflicting values are handled. Done should include the proposed backwards-compatible lookup behavior and coverage for both new-name and old-name configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100