promote links to file assets unless we already know they are pages#1354
Open
promote links to file assets unless we already know they are pages#1354
Conversation
This file contains hidden or 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
1 participant
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.
closes #639
Note: in #639 Mike mentions “remove
.md”, which I take as a suggestion that we might want a link to[page.md](page.md)to be considered as a link to the page.With this PR I don't apply that change, and instead a link to
[page.md](page.md)results in a file asset with the source markdown. If that is not what we want, then we could add.mdto the skip list.I also wonder if we need to treat
a[href][download]as always linking to a file?