Ignore deprecation error in WPCS until 3.0 is ready to be used #34
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use a fix from WordPress/WordPress-Coding-Standards#2035 (comment) to allow the coding standards to be used against PHP 8.0+ without requiring any extra Composer repository.
It looks as if https://github.com/Automattic/VIP-Coding-Standards preparing to release a new version soon that will require WPCS 3.0 given the latest changes in their
developbranch. In the meantime, we can allow our projects to use the Alley Coding Standards against PHP 8.0+ without needing a Composer workaround. Upgrading to PHP 8.1 will be as simple ascomposer updateto make PHPCS happy.