Skip to content

Conversation

antonioeatgoat
Copy link
Contributor

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes/features)
  • Docs have been added/updated (for bug fixes/features)

What kind of change does this PR introduce?
New rule is added to the ruleset.

What is the current behavior?
Both !$variable and ! $variable pass the check.

What is the new behavior?
Only !$variable pass the check.

Does this PR introduce a breaking change?
No.

Other information:
I used the rule from PHP_CodeSniffer itself and not the one from Slevomat as suggested in the issue. I realized that the one from Slevomat was actually checking for - instead of !, and anyway there was no reason for not using this existing one.

@antonioeatgoat antonioeatgoat linked an issue Jun 28, 2024 that may be closed by this pull request
1 task
@antonioeatgoat antonioeatgoat changed the title Fore zero spaces after Not operator Force zero spaces after Not operator Jun 28, 2024
@antonioeatgoat antonioeatgoat marked this pull request as draft June 28, 2024 16:12
@antonioeatgoat antonioeatgoat marked this pull request as ready for review July 3, 2024 16:16
@Chrico Chrico self-requested a review July 3, 2024 16:28
@antonioeatgoat antonioeatgoat merged commit 34173b3 into version/2 Jul 5, 2024
@antonioeatgoat antonioeatgoat deleted the 92-enforce-no-space-after-negation-operator branch July 5, 2024 08:13
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.

[Feature Request]: Enforce no space after negation operator

4 participants