-
Notifications
You must be signed in to change notification settings - Fork 12
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
move amendments and imports under project_modifiers #344
Comments
Arguments for:
Arguments against:
Overall I think it makes sense to use |
Slight preference for the more hierarchical |
So currently those exist as project-level keys, right? And functionally, "amendments" is basically like what was "subprojects?" |
If that understanding is roughly true, I agree w/ @afrendeiro . My preference isn't strong either, but I like the parallel structure that's gained by making it hierarchical rather than a "level up," and I think it fits nicely w/ the Python tenet of explicit-over-implicit. |
yes
Yes, except for the fact that you can activate multiple at once |
Nice! 🔥 |
amendments
andimports
to fall underproject_modifiers
?the it'd be:
Originally posted by @nsheff in #342 (comment)
The text was updated successfully, but these errors were encountered: