Update deprecated check to consider new annotations #4108
Merged
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.
Work towards #4107
With the new
@Deprecated
annotations, we don't want to consider any@Deprecated
annotatation as announcing "this thing is deprecated!" and cross it out. Instead, we should only consider@deprecated
(the constant) and@Deprecated()
(the unnamed constructor) as announcing such a thing.All this change does is fix
isDeprecated
to understand that@Deprecated.extend
etc does not mark the element as deprecated.There should be future changes where we do indicate something about a specific deprecation, like
@Deprecated.extend
.