Juliette

Ha! Managed to still find one bug in the original PR. (support for array properties with `extend="true"` was broken) As it looks like no-one has started reviewing this PR yet,...

PHPCS is often used within IDEs during live coding, so, generally speaking, it will ignore parse errors. Along the same lines, something which may be a parse error in one...

There must be something wrong with how you're calling PHPCS in that case, as on PHP 8.1 (and other PHP versions), I get the expected error with your code sample:...

> I'm using version 3.6.1 and you are using version 3.6.2, could that be the difference? I'm running on Windows too, not sure if that makes a difference or not?...

Just for context: PSR2 (and PSR12 for that matter) were published before trailing comma's in function calls were allowed (PHP 7.3), so the fact that the PSRs don't allow/forbid those...

1. Do you have a code sample demonstrating the conflict ? 2. Could that code sample be added to the test file ? 3. As for referencing another sniff via...

@nvuillam Just FYI: external repositories/standards can use their own reports. For more information on how to do so, see these issues/PRs: * https://github.com/squizlabs/PHP_CodeSniffer/issues/1942 * https://github.com/squizlabs/PHP_CodeSniffer/pull/1948

Also just looked at the specs and ... jeezs louise.... who's got the time to even read that, let alone implement it ? This would require a study of that...

Well, a lot of what you are describing here is explained in https://github.com/squizlabs/PHP_CodeSniffer/wiki/Coding-Standard-Tutorial Once you have created your external standard, you will also need to register it with PHPCS using...

This is not currently possible with PHPCS. Generally speaking, either allowing a sniff to be customized via properties or a sniff having (very) modular error codes, which would allow to...