Improve go-to-definition for object pattern field aliases #242
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.
Previously, go-to-definition on
B
withimport { A = B } "path/to/A"
would resolve to the location ofB
in the import. Now, the language server automatically follows the import and places the cursor on the definition ofA
. This has the additional benefit of showing tooltip doc comments (which use the go-to-definition logic behind the scenes) in more situations.