feat: introduce black flags #403
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Sorry for the mess, we revamed module structure in #397, could you port these changes over? |
benhiemer
force-pushed
the
feat-add-black-flags
branch
from
f821893 to
8fc4dd7
Compare
|
No problem. I like the new |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds
setting.black.flagsmaking theblackhook more configurable. Default is no flags.All options are listed here, it is documented in the nix option.
I first thought about mirroring all options but this way is more flexible imho. My primary intention is to support
--experimental-string-processingwith this (which will change to--preview --enable-unstable-feature string_processingin black v24, see the change logs, another advantage of a genericflagsargument). Of course, further options for specific arguments can be added later.