fix for trailing slash problem - updating links to use file path instead of URL path #565
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
Adding new GA4 ID to test if it works for conceptual pages
Fixing links to use file path instead of url path; trailingSlash false
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.
Fix for trailing slash problem.
When a user accessed the docs with a URL that ended in a backslash, the relative URL links to a related topic in the same directory failed.
Converted links to relative file paths (added file extension).
Tried setting
trailingSlashtofalsebut that broke the build on GitHub. Worked fine for local builds. For some reason, the relative file path fixed the problem (for now).Updated the publish sandbox extensions section and removed link to the form (no longer exists). Pointed to the Design Guide topic.