fix: support fragments in image URLs #753
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
joaomoreno
approved these changes
Jul 15, 2022
|
🎉 This PR is included in version 2.9.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
This PR fixes #739 by taking the
#character into account in image URLs.Description
When inserting images in a markdown file using the HTML tag, relative image URLs that contain a
#character do not get prefixed with the base URL.Later when validating image URLs, a relative URL is passed to the
URLconstructor, which results in an error being thrown.vscode-vsce/src/package.ts
Lines 779 to 782 in 955c760
Fixes
The regex responsible for replacing![]()
links has been modified to support the
#character.I have also updated the test suite accordingly.