[Feature Request] Save customized controller autoconfig files in a separate directory from downloaded/auto updated ones
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
When you currently customize a controllers autoconfig files via "Save Controller Profile" it will overwrite the autoconfig file in the autoconfig, if you next update the controller auto configurations via the online updater, it will overwrite it, it would be nicer if they are saved in a separate directory that takes precedence to avoid this behavior.
Contributor guide
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 the "Save Controller Profile" flow and the online updater's handling of controller autoconfig files. Determine how the autoconfig directory is selected and how profiles are loaded, then verify that saved custom profiles remain after an update and take precedence over downloaded profiles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100