Skip to content

Conversation

@jrfnl
Copy link
Member

@jrfnl jrfnl commented Apr 11, 2021

As per #1163:

  • Deprecations should throw warnings.
  • Removals should throw errors.
  • Both should use a different error code.

Note: the RemovedAssertStringAssertion sniff is new to PHPCompatibility 10.0.0, so this error code change has no consequences.
The error code change for the RemovedTernaryAssociativity should be noted in the changelog though as the sniff was introduced in PHPCompatibility 9.2.0.

Fixes #1163

As per 1163:
* Deprecations should throw warnings.
* Removals should throw errors.
* Both should use a different error code.

Note: the `RemovedAssertStringAssertion` sniff is new to PHPCompatibility 10.0.0, so this error code change has no consequences.
The error code change for the `RemovedTernaryAssociativity` should be noted in the changelog though as the sniff was introduced in PHPCompatibility 9.2.0.

Fixes 1163
@jrfnl jrfnl added this to the 10.0.0 milestone Apr 11, 2021
@jrfnl jrfnl requested a review from wimg April 11, 2021 21:33
@wimg wimg merged commit 396c8c1 into develop Apr 17, 2021
@wimg wimg deleted the feature/1163-message-type-code-review branch April 17, 2021 15:19
@jrfnl jrfnl removed PR: quick merge PR only contains relatively simple changes PR: ready for review labels Apr 17, 2021
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.

Do an error/warning consistency check across the codebase

3 participants