The drupal preset writes the trailing comma, the indentation and the line breaks of a long array.
Codes
Handled by
ArrayClosingIndentation, ArrayIndentation
mago format, partly
CommaLastItem, LongLineDeclaration
mago format
ArrayClosingIndentation: An array that opens on a continuation line gets the indent of the statement's first line. Coder counts from the line the array opens on, and reports its items and closing bracket.
ArrayIndentation: When the value after => is a ?? chain that breaks over lines, the formatter writes the next lines at the key's indent. Coder wants them one level deeper. The formatter also writes the broken && or || condition of a ternary in an array element at the element's indent, and breaks an array at a block comment between its elements, and Coder reports both.
CloseBraceSameLine: drupal/post-statement-comment reports a comment after the closing brace of a class, such as } // end class. The formatter moves code after the brace to a line of its own and removes trailing spaces. A ?> after the brace isn't reported when HTML follows it. At the end of a file, no-closing-tag reports the tag and the formatter removes it.
MissingBrace: A class without braces doesn't parse. Mago reports a parse error, and the formatter skips the file.
MissingShort: A phpcs: line above the summary is skipped, and the line below it counts as the summary. Coder reports it. In Drupal core, only the KernelTests, Unit and FunctionalJavascript directories are checked, as in core's phpcs.xml.dist.
TemplateSpacingAfterComment: A blank line between the file docblock and the ?> that follows it, in a file of any extension. Not ported.
WrongStyle: A // @codingStandardsIgnoreFile comment at the start of a file isn't reported under this code. drupal/missing-file-comment reports the file instead. The fix converts a comment only when a blank line follows it.
ExtraParamComment: mago analyze reports a @param whose name isn't a parameter, and drupal/doc-tag-descriptions one that repeats a name.
InvalidNoReturn: Reported on the function, not on the @return tag.
InvalidReturnVoid: Reported on the return statement, not on the @return void tag. A yield in such a function is reported as invalid-generator-return-type.
ParamNameNoMatch: drupal/doc-tag-descriptions reports a repeated @param, one that is out of order, and a & on a parameter that isn't taken by reference. mago analyze reports a name that isn't a parameter, and a ... on a parameter that isn't variadic.
Empty: Mago's rule. It also reports an empty /* */, which Coder doesn't. Its fix leaves a blank line where phpcbf removes the line.
SpacingAfter: The rule leaves the blank line between a comment and a closing bracket to the formatter. Before the closing brace of a class, interface, trait or enum with members the formatter always writes one, and Coder reports it.
IncorrectVarType: Coder runs the whole @var line, description included, through its type check, so it also reports a description with a ., ;, ! or = in it. The rule checks only the type.
NewlineAfterOpenBrace: The formatter writes a match with one arm on one line, and Coder reports that line under this code and under OpenBracketSpacing.OpeningWhitespace, CloseBracketSpacing.ClosingWhitespace and ScopeClosingBrace.Line.
Coder also checks .txt and .md files, which aren't read by Mago, and the YAML files of a config directory, which drupal.mago.toml leaves out of the linter.
The rule doesn't report the keys below the comment of the drupal.org packaging script. Coder reports them, so it reports every module installed by Composer. The rule reads .info.yml files only, and the same keys in a Drupal 7 .info file need phpcs. Both tools skip the version key of a file under a core directory. Coder looks for /core/ in the absolute path, and the rule in the path from the workspace.
Mago's rule, on by default, with a fix that needs --potentially-unsafe. Its list of aliases doesn't have gzputs(), _() and pg_clientencoding(), which Coder reports.
The formatter writes <?php } for a closing brace after inline HTML, and Coder reports the space. Coder also reports the match with one arm that the formatter writes on one line, and the space that the formatter keeps before ) in a parameter list that holds only a comment, as in function f( /* $x */ ).
The formatter keeps a space between an opening bracket and a comment that follows it, as in foo( /* note */ $x), and Coder reports that space. Coder also reports the match with one arm that the formatter writes on one line, and the space it writes after ( in a parameter or argument list that holds only a comment, as in f( /* $x */ ).
IncorrectExact: The formatter gives a comment between a break, return or throw and the next case the indent of the case body. Coder wants the indent of the case label there, and reports it. The formatter also indents a break after a return in the same case, which the analyzer reports as useless-control-flow. It writes an anonymous class with attributes with a line break after new and the body one more level in. Coder reports the body's indent, and the line break as LanguageConstructSpacing.IncorrectSingle.