evlli/hass-core
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Remove ignore-wrong-coordinator-module in pylint CI (#117479)

Browse source
This commit is contained in:
epenet 2024-05-15 11:51:14 +02:00 • committed by GitHub
parent 6116caa7ed
commit 73ed49e4b7
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 2 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
.github/workflows/ci.yaml vendored
View file

@ -611,14 +611,14 @@ jobs:
run: |
. venv/bin/activate
python --version
pylint --ignore-missing-annotations=y --ignore-wrong-coordinator-module=y homeassistant
pylint --ignore-missing-annotations=y homeassistant
- name: Run pylint (partially)
if: needs.info.outputs.test_full_suite == 'false'
shell: bash
run: |
. venv/bin/activate
python --version
pylint --ignore-missing-annotations=y --ignore-wrong-coordinator-module=y homeassistant/components/${{ needs.info.outputs.integrations_glob }}
pylint --ignore-missing-annotations=y homeassistant/components/${{ needs.info.outputs.integrations_glob }}
mypy:
name: Check mypy

15
pylint/plugins/hass_enforce_coordinator_module.py
View file

@ -19,24 +19,9 @@ class HassEnforceCoordinatorModule(BaseChecker):
"Used when derived data update coordinator should be placed in its own module.",
),
}
options = (
(
"ignore-wrong-coordinator-module",
{
"default": False,
"type": "yn",
"metavar": "<y or n>",
"help": "Set to ``no`` if you wish to check if derived data update coordinator "
"is placed in its own module.",
},
),
)
def visit_classdef(self, node: nodes.ClassDef) -> None:
"""Check if derived data update coordinator is placed in its own module."""
if self.linter.config.ignore_wrong_coordinator_module:
return
root_name = node.root().name
# we only want to check component update coordinators