-
Notifications
You must be signed in to change notification settings - Fork 1.4k
RFC: configuration utilities #3652
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
Conversation
cc @yim-lee |
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.
Thanks for taking on this work, @tomerd. I'd be very happy to see the logic for configuration consolidated and refactored into a single, consistent API.
Overall, this is looking good. The only question I have is whether Configurations
should be its own module, rather than part of the Workspace
module. What would the benefit be of having a new module versus, for example, putting all of this in a Configuration
subfolder within the Workspace
module.
38cb45e
to
6310e79
Compare
motivation: with SE-0292 adding more configuration, refactor the configuration uttilities to their own module so they can be used consistently across the code changes: * create a new Configuration module * refactor Collections sources storage to use the configuration module * refactor Mirrors to use the configuraiton module * refactor netrc to use the configuraiton module * adjust and add tests
6310e79
to
ffbaa1c
Compare
thanks for the reminder @mattt - I think we can call this done for this phase |
motivation: with SE-0292 adding more configuration, refactor the configuration uttilities to their own module so they can be used consistently across the code
changes: