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

WhiteSpace/OperatorSpacing: add extra test #2430

Merged
merged 1 commit into from Mar 5, 2024

Conversation

jrfnl
Copy link
Member

@jrfnl jrfnl commented Mar 5, 2024

Upstream a PR is open - and will be merged soon - to change the protection against the Squiz sniff, which this sniff extends, handling operators found in declare() statements. In particular, the PR is about how the sniff handles parse errors/live coding for declare statements.

As the WPCS sniff calls the parent register() method and falls through to the parent process() method, the WPCS sniff should automatically get that extra protection too.

This commit just adds an extra test to the WordPress.WhiteSpace.OperatorSpacing to safeguard things.

Upstream a PR is open - and will be merged soon - to change the protection against the `Squiz` sniff, which this sniff extends, handling operators found in `declare()` statements.
In particular, the PR is about how the sniff handles parse errors/live coding for declare statements.

As the WPCS sniff calls the parent `register()` method and falls through to the parent `process()` method, the WPCS sniff should automatically get that extra protection too.

This commit just adds an extra test to the `WordPress.WhiteSpace.OperatorSpacing` to safeguard things.
@dingo-d dingo-d merged commit 8b1a52e into develop Mar 5, 2024
46 checks passed
@dingo-d dingo-d deleted the feature/operatorspacing-sync-with-upstream-289 branch March 5, 2024 10:47
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.

None yet

3 participants