Tests: introduce resolve and code completion contexts #18647
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.
This PR replaces the manual context creation with locating a
{caret}
mark in the source in more tests. It makes it much easier to write new editor-related tests and should also prevent mistakes that are easy to make when providing the context by hand. It continues the work started in #18524 and #18609.To make it easier to use the FCS APIs it introduces several new types:
SourceContext
: contains info about the cursor position and the line textResolveContext
: contains data needed for resolve-related features (getting a symbol, tooltip, overloads, etc)CodeCompletionContext
: similar toResolveContext
but has code completion-specific differencesIt also introduces new
Checker
module that provides test helpers for working with these new contexts. We may evolve these helpers into a newer FCS API in future, as it makes it significantly easier to work with these contexts than to provide things like the cursor coordinates separately.