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

feat(PER-CS2.0): The fn keyword MUST NOT be succeeded by a space. #7355

Closed
wants to merge 1 commit into from

Conversation

SpacePossum
Copy link
Contributor

@SpacePossum SpacePossum commented Oct 4, 2023

@ see https://github.com/php-fig/per-coding-style/blob/2.0.0/spec.md

The fn keyword MUST NOT be succeeded by a space.

after #7247 can be updated

@SpacePossum SpacePossum changed the title PER - The fn keyword MUST NOT be succeeded by a space. feat(PER-CS2.0): The fn keyword MUST NOT be succeeded by a space. Oct 4, 2023
@coveralls
Copy link

Coverage Status

coverage: 94.581% (+0.002%) from 94.579% when pulling 8b791a0 on SpacePossum:PER_FN_follow into 84dd90e on PHP-CS-Fixer:master.

Comment on lines +39 to +41
'closure_fn_spacing' => 'none',
'closure_function_spacing' => 'one',
'trailing_comma_single_line' => false,
Copy link
Member

Choose a reason for hiding this comment

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

If I understand right, only closure_fn_spacing is non-default here.
I suggest to explicitly configure closure_fn_spacing only in that case, and make a TODO for fixer to change default for closure_fn_spacing in next major

@Wirone
Copy link
Member

Wirone commented Oct 10, 2023

I believe it's a duplicate of #6970 🙂.

@SpacePossum SpacePossum deleted the PER_FN_follow branch October 10, 2023 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants