Better error message for invalid exclude types#3764
Conversation
| - Fix black not honouring `pyproject.toml` settings when running `--stdin-filename` and | ||
| the `pyproject.toml` found isn't in the current working directory (#3719) | ||
| - Black will now error if `exclude` and `extend-exclude` have invalid data types in | ||
| `pyproject.toml`, instead of silently doing the wrong thing. |
There was a problem hiding this comment.
| `pyproject.toml`, instead of silently doing the wrong thing. | |
| `pyproject.toml`, instead of silently doing the wrong thing. (#3764) |
There was a problem hiding this comment.
Github is doing something really weird where the pushes show on the branch in my fork, but don't get reflected in the PR hauntsaninja@9f55e73
There was a problem hiding this comment.
Yeah seems like there is something weird going on. In any case, this PR looks good once GitHub cooperates.
There was a problem hiding this comment.
For whatever reason, the force in force push seems to wake it up. So I just need to commit an empty commit, push it, delete the commit and force push.
There was a problem hiding this comment.
Sounds like a great workflow
|
diff-shades reports zero changes comparing this PR (9f55e73) to main (8e618f3).%0A%0A---%0A%0AWhat is this? | Workflow run | diff-shades documentation |
2 participants
Currently if this is a list, this ends up using the repr of the list as a regex.
Fixes #3574, fixes #3754