Accept default= in modify_defaults #1339
Merged
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.
Closes #1336 and closes #1338
Handling it in
linters_with_defaults()
alone is pretty painful because of thesubstitute()
-based logic for auto-naming, so I implemented the patch insidemodify_defaults()
instead.Originally wanted to just throw a warning with
modify_defaults()
too, but it seems unlikely to usedefault=
by accident there becausedefaults=
is a required argument. So added some uglier logic to allowmodify_defaults(default = , ...)
to work, assuming that was intentional.