Repository navigation
fix: use forward slashes in tag page links on Windows - #603
Merged
Merged
Conversation
Pages in the user guide, recipes and custom sections were identified by their path written with the operating system's separator. On Windows, the links on tag pages and the page keys in the tag and page-status data held backslashes, such as `user-guide\advanced\intro.qmd`. These paths now always use `/`.
📚 Preview this PR's docs locallyFetch the just-built site and open it in your browser: # this exact build
great-docs preview --run 42131556244
# or always the latest build for this PR
great-docs preview --pr 603Auth & tips
|
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
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.
On Windows, the links on tag pages and the page keys in the tag and page-status data for the user guide, recipes and custom sections held backslashes, such as
user-guide\advanced\intro.qmd. The paths came from the operating system's separator, so the links did not resolve on the built site.These paths now always use
/. Builds on macOS and Linux are unchanged.