-
Notifications
You must be signed in to change notification settings - Fork 11
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
ENH: Creates a config.yaml file to hold badger's settings #82
Conversation
…on for validating and holding the configuaration data. a few bug remain and there are two more features needed for this feature to be complete
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, need to remove some commented out lines if we don't need to
Also need to resolve merge conflicts |
I removed the commented out code and fixed the merge conflict. let me know if there is anything else needed on this PR |
@wenatuhs this is ready to go if you don't have any changes needed on your side |
Description
This PR creates a config.yaml file to hold badger's settings. it also changed the internal plumbing of the settings. Changing from a design which used global variables paired with QSettings to a design which uses pydantic class which holds the default settings, a config file which badger loads in to replace the default settings and a singleton to hold the settings and pipe it throughout the rest of the application.
How Has This Been Tested?
Unit tests need to be added to make this PR ready for release
Where Has This Been Documented?
Auto documentation has been added to all new methods.
The process will be noted on the website
Screenshots: