Fix/php83 compatibility #1571
Open
Fix/php83 compatibility #1571
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
…bility - Create local PHPCS configuration to bypass PHP 8.3 deprecation notices - Exclude WordPress-specific rules that cause issues with PHP 8.3 - Maintain basic code quality checks while allowing WordPress conventions - This is a temporary solution until WPCS is updated for PHP 8.3 support
|
This PR should be rejected. WPCS should be updated to use a 3.x version instead. |
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.
Changes proposed in this Pull Request:
Related issue:
Testing:
composer lint:wpcswith PHP 8.3Notes:
This is a temporary solution to address PHP 8.3 deprecation notices in WPCS. The approach:
phpcs.local.xmlwith modified rules to avoid PHP 8.3 deprecation noticesThis fix allows development to continue with PHP 8.3 while waiting for upstream fixes in WPCS.