UpdateTypeInfo for all file that has errors for any edit #905
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.
What does this PR do?
Update Apex LSP jar to fix issue where references might go stale when edits are applied in a certain order.
What issues does this PR fix or reference?
This fixes the problem in Apex LSP which may surface more often with refactorings enabled where when edits are applied in a certain order may result in stale references. We now update the typeinfos for all the error files on edits to avoid stale references in error files.
@W-5573514@