Skip to content

Comments

Updated doctrine/coding-standard to 6.0#178

Merged
Ocramius merged 1 commit intodoctrine:masterfrom
patrickjahns:bump-coding-standard
Mar 17, 2019
Merged

Updated doctrine/coding-standard to 6.0#178
Ocramius merged 1 commit intodoctrine:masterfrom
patrickjahns:bump-coding-standard

Conversation

@patrickjahns
Copy link
Contributor

Updated coding-standard and used phpcbf to automatically fix them

Signed-off-by: Patrick Jahns <github@patrickjahns.de>

return static function ($a, $b) use ($name, $next, $orientation) : int {
$aValue = ClosureExpressionVisitor::getObjectFieldValue($a, $name);

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems incorrect

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I revert the change - codesniffer screams:

FILE: lib/Doctrine/Common/Collections/Expr/ClosureExpressionVisitor.php
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
FOUND 1 ERROR AFFECTING 1 LINE
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 104 | ERROR | [x] Expected 1 lines after "return", found 0.
     |       |     (SlevomatCodingStandard.ControlStructures.ControlStructureSpacing.IncorrectLinesCountAfterControlStructure)
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------
PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Need to have a closer look into the slevomat rules to figure out whats going wrong here

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you reproduce this and report it to doctrine/coding-standard maybe? We can roll with this patch meanwhile 👍

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Boiled it down to a simple example and open report here: slevomat/coding-standard#635

@Ocramius Ocramius self-assigned this Mar 17, 2019
@Ocramius Ocramius added this to the 1.6.0 milestone Mar 17, 2019
@Ocramius Ocramius merged commit d156588 into doctrine:master Mar 17, 2019
@patrickjahns patrickjahns deleted the bump-coding-standard branch March 17, 2019 17:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants