Juliette

@Rasmus-Bertell I would consider a PR to add that as a feature in PHPCS 4.0 - allow scanning hidden files, but only when the file is explicitly declared by name...

Understood. I'll leave the ticket open for now. There may be others interested in the feature and/or interested on working on the feature. If not, we can always still close...

@hirasso Thanks for bringing this up. There is an [open PR for this](https://github.com/squizlabs/PHP_CodeSniffer/pull/3661) in the old repo, however, that PR was blocked because PSR-PER (the successor of PSR12) in their...

@AlexSkrypnyk Scanning files without extension is a completely different thing and is already on the [roadmap for the 4.0 release](https://github.com/squizlabs/PHP_CodeSniffer/issues/2916). Scanning (and by extension auto-fixing) hidden files is what this...

Closing as there has not been any additional interest.

When addressing this change, I believe there is a related bug, which should also be looked into and fixed: the use of context sensitive keywords as goto labels. As things...

Reminder for the tests: * Test with named parameters and make sure the labels are not tokenized as goto labels: `callMe(label: $a, other: $b)`

@przemekhernik Just checking in to see when you have time to finish this off ... ?

@montala-alinc While I agree this behaviour is unexpected, I'm not sure it is a bug in PHPCS. PSR12 is pretty clear about how control structure braces should be formatted and...

@GaryJones @Ocramius @sirbrillig @stronk7 Thank you for your input so far. I'm going to leave this issue open a little longer to give more people the chance to pitch in,...