Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run HeaderCommentFixer after NoBlankLinesAfterPhpdocFixer #3987

Conversation

StanAngeloff
Copy link
Contributor

@StanAngeloff StanAngeloff commented Aug 31, 2018

This ensures the output is stable when HeaderCommentFixer is configured with ["separate" => "bottom", "commentType" => "PHPDoc"] and the target file has no namespace or declare() construct.

Test case added, test suite passes.

@SpacePossum SpacePossum added this to the 2.12.5 milestone Nov 1, 2018
@SpacePossum
Copy link
Contributor

Thanks for this PR @StanAngeloff! Looking good so far, not sure what is/was up with circleci, lets see what it does now

@keradus keradus force-pushed the improvement-change-header-comment-priority branch from ca349a2 to da3bdea Compare November 28, 2018 00:05
@keradus
Copy link
Member

keradus commented Nov 28, 2018

Thank you @StanAngeloff.

@keradus keradus merged commit da3bdea into PHP-CS-Fixer:2.12 Nov 28, 2018
keradus added a commit that referenced this pull request Nov 28, 2018
…StanAngeloff)

This PR was merged into the 2.12 branch.

Discussion
----------

Run HeaderCommentFixer after NoBlankLinesAfterPhpdocFixer

This ensures the output is stable when `HeaderCommentFixer` is configured with `["separate" => "bottom", "commentType" => "PHPDoc"]` and the target file has no `namespace` or `declare()` construct.

Test case added, test suite passes.

Commits
-------

da3bdea Run HeaderCommentFixer after NoBlankLinesAfterPhpdocFixer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants