-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config system should be changed so that people don't have to update their personal config everytime an option is added #79
Comments
Ok done now, I made a yaml config, look in the readme for instructions |
If you find any errors please report |
There were many issues. You should really test your code and make sure it works. Anyways, I fixed them all in #80 |
You are right... I should also write some automated tests. |
Respected Dev(s) |
This was recently fixed in the latest update. To update, run |
Right now, every time a config option is added, users are expected to manually go update their config_personal.py file with the new option that was added to continue to be able to use the program. I think that this project should use a config system where there are 2 config files: a defaults one and one that stores the user changed options.
All of the default options are stored in the default config file and then users can manually go through and add every option they want changed into the custom config file with the updated value.
This would solve the issue of new config options breaking the program and the messy code required to use a hard-coded default in case a config option is not set.
The text was updated successfully, but these errors were encountered: