Support split strings within inspections & method target references #2358
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.
Description:
Currently some inspections don't support strings that have been split to support a line width limit, same goes for Injection method targets.
Changes:
Removed multiple direct
PsiLiteral
checks which where not needed, since all calls would lead toPsiElement.constantStringValue
, which will returnnull
if its not suppose to.Now, all these calls will use the
ConstantExpressionVisitor.compute
call which takes care of the split string logic.Examples:
Method Reference
Before - Single (Expected behaviour)
Before - Split
After - Split
AmbiguousReferenceInspection
Before
After
InvalidMemberReferenceInspection
Before
After
UnnecessaryQualifiedMemberReferenceInspection
Before
After