[CodeQuality] Deprecate TypeNullableEntityFromDocblockRector - #518
Merged
Conversation
…pinionated and narrow use-cased
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
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.
TypeNullableEntityFromDocblockRectoris the only non-deprecated rule not part of any set. It is too opinionated and narrow use-cased to belong in a general code-quality set: it blindly forces all entity properties to nullable native types read from docblocks — a niche stepping-stone, not a broadly safe cleanup.Deprecating it (joins the 4 already-deprecated orphan rules in
CodeQuality/Rector/Class_).Change
DeprecatedInterface+@deprecateddocblock