You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it's reasonable to expect that HM Linter will run as normal, and use 1.1.1 for PHPCS. What actually happens is that PHPCS uses 1.1.1, but is also marked as disabled so no sniffs are run.
Because this merge clobbers any keys from the defaults in a non-recursive fashion, enabled is not set on the resulting configuration option and PHPCS does not run.
The text was updated successfully, but these errors were encountered:
(This could be fixed either by recursively merging config, or else making enabled default to true if the property is missing)
We'll need to recursively merge, as linters can be set as disabled by default (i.e. stylelint when introduced was disabled by default); you could argue that setting the version implicitly enables it though I guess.
When you create a yaml file like this:
it's reasonable to expect that HM Linter will run as normal, and use 1.1.1 for PHPCS. What actually happens is that PHPCS uses 1.1.1, but is also marked as disabled so no sniffs are run.
The default configuration includes a nested property
enabled: true
(config.js):The defaults are then merged in here:
Because this merge clobbers any keys from the defaults in a non-recursive fashion,
enabled
is not set on the resulting configuration option and PHPCS does not run.The text was updated successfully, but these errors were encountered: