Linting with the new version of Black 23.1 #935
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
MatthiasZepper
force-pushed
the
Linting_Black23.1
branch
from
0012b42
to
6b86d7f
Compare
|
I have no issues with the python code new lint, but concerned by the new json lint |
|
Fair enough. Linting the JSON seems to have crashed the whole thing... :-( I am gonna to revert... |
maxulysse
approved these changes
Feb 3, 2023
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 is solely to fix linting errors raised by the CI due to updates to black. No other changes have been made herein.
My other PR (#934) has been rebased on this branch according to a suggestion by @mashehu on Slack.