Parse position or selection from link fragment #2049
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rchl
reviewed
Sep 11, 2022
rchl
approved these changes
Sep 11, 2022
rchl
approved these changes
Sep 12, 2022
rchl
reviewed
Sep 12, 2022
rchl
approved these changes
Sep 12, 2022
rchl
added a commit
that referenced
this pull request
Sep 27, 2022
* main: Parse position or selection from link fragment (#2049)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Should handle the following formats which are supported by VSCode:
https://github.com/microsoft/vscode/blob/835ace5796cec0ed19a7eec119b26b57220b0f1a/src/vs/platform/opener/common/opener.ts#L153-L160
It applies to Markdown links in the hover content and also to
DocumentLink.targetfrom the "Document Link" response.Can be tested for example with LSP-html and the following file:
Closes #2009.