Juliette
Juliette
> Failure is from HTTP 405 error when uploading code coverage, which I think is unrelated to the actual changes 💯 Coveralls is doing some disruptive maintenance: https://status.coveralls.io/ (also the...
Thanks @DanielEScherzer. I'm hoping to take another look over the next few days, but what with the PRs for 4.0 being lined up (see #924), I may delay this PR...
P.S.: I see there is another merge conflict. Sorry about that. PR #948 also touches that same sniff, so you may want to hold off resolving the conflict until that...
@joachim-n Thank you for reporting this. This is due to the sniff incorrectly acting on short lists. The `Squiz.Arrays.ArrayDeclaration` sniff is [known to be problematic and has been for years](https://github.com/squizlabs/PHP_CodeSniffer/issues/582)....
Loosely related to #527
@joachim-n Can this issue be closed ?
@jacobcassidy Good question. AFAICS, the [PER standard](https://www.php-fig.org/per/coding-style/) does not have rules about this. Might be an idea to open an issue in the [PER repo](https://github.com/php-fig/per-coding-style/issues) ? Independently of the outcome...
@utdrmac Double arrow alignment in array assignments is a completely different topic. Have a look at the `Squiz.Arrays.ArrayDeclaration` sniff for that.
@utdrmac As I said before, questions regarding array arrow alignment do not belong in this ticket, which is about **match** arrow alignment.
The rule could also be along the lines of the below: > For multi-line arrays, keyed lists and match control structures: > Either align all arrows to the widest key...