Open relative files to the project root from markdown preview #2715
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
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.
I have a project hosted in Azure DevOps and for proper navigation within markdown files I have to use absolute links relative to the project, like
/documentation/service.md.A link like
[documentation](/documentation/service.md)opens properly from the editor, but from the preview window this results in an error "Browser configuration problem - The file /documentation/service.md does not exist". While the path is relative to the project root from the editor, it seems like this is treated as an absolute path from the preview window.With this PR the current behavior is extended to also check if there is also a file that is relative from the project root when it could not be found as an absolute file.