Fix relative URLs in reference #84
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
fredericsimard
approved these changes
Mar 4, 2024
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.
Problem
When clicking an anchor in the Table of Contents of the reference on https://gbfs.org/specification/reference/, the links redirect to the raw content on GitHub.
Solution
This PR fixes anchors in the reference.
The reference is fetched by the plugin mkdocs-embed-external-markdown. The plugin change log shows that version
3.x.x:We want the relative links to remain relative. So this PR downgrades the plugin to the version preceding this change:
2.3.0.Before
Screen.Recording.2024-03-04.at.10.07.50.mov
After
Screen.Recording.2024-03-04.at.10.08.43.mov