[Merged by Bors] - fix(lint-style.py): recognise all kinds of style exceptions#16297
[Merged by Bors] - fix(lint-style.py): recognise all kinds of style exceptions#16297
Conversation
PR summary 0c387bcf7aImport changes for modified filesNo significant changes to the import graph Import changes for all files
Declarations diffNo declarations were harmed in the making of this PR! 🐙 You can run this locally as follows## summary with just the declaration names:
./scripts/declarations_diff.sh <optional_commit>
## more verbose report:
./scripts/declarations_diff.sh long <optional_commit>The doc-module for |
Not recognising one is more confusing than any other behaviour. In practice, after #15610 none of these should be needed in practice.
35b62b7 to
0c387bc
Compare
|
Thanks! maintainer merge If I understand correctly, the general trend is to eliminate all the error codes that are maintained by the python/bash linters. However, this means that if for some reason one of these error codes creeps up again, the script will not be confused, right? |
|
🚀 Pull request has been placed on the maintainer queue by adomani. |
|
To clarify: all errors added are maintained by In the medium-term, I would propose removing |
|
Thanks! 🎉 |
Currently, some style exceptions emitted by the `lint-style.py` script are not recognised by that same script. This can lead to confusing behaviour. That said, all current exceptions should rather be fixed than excepted - so this is unlikely to be an issue in practice.
|
Pull request successfully merged into master. Build succeeded: |
Currently, some style exceptions emitted by the `lint-style.py` script are not recognised by that same script. This can lead to confusing behaviour. That said, all current exceptions should rather be fixed than excepted - so this is unlikely to be an issue in practice.
Currently, some style exceptions emitted by the `lint-style.py` script are not recognised by that same script. This can lead to confusing behaviour. That said, all current exceptions should rather be fixed than excepted - so this is unlikely to be an issue in practice.
Currently, some style exceptions emitted by the `lint-style.py` script are not recognised by that same script. This can lead to confusing behaviour. That said, all current exceptions should rather be fixed than excepted - so this is unlikely to be an issue in practice.
Currently, some style exceptions emitted by the
lint-style.pyscript are not recognised by that same script. This can lead to confusing behaviour.That said, all current exceptions should rather be fixed than excepted - so this is unlikely to be an issue in practice.