Fix deprecation notice in Inpsyde ruleset.xml #105
Merged
Conversation
This file contains hidden or 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
Inpsyde ruleset.xml used a comma-separated string for array configurations, which is now deprecated and will break in PHPCS 3.0 Signed-off-by: Giuseppe Mazzapica <[email protected]>
Chrico
approved these changes
Aug 11, 2025
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix
What is the current behavior? (You can also link to an open issue here)
Inpsyde ruleset.xml used a comma-separated string for array configurations, which is deprecated since PHPCS 3.3 and will break in PHPCS 4.0. See release notes
What is the new behavior (if this is a feature change)?
The new syntax
<property ... type="array"><element key="..." value="..."></property>is used.Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No.
Other information: