wip: handle folders changing between versions - #494
Draft
eoghanriley wants to merge 2 commits into
Draft
Conversation
✅ Deploy Preview for uds-product-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
This example shows what it would be like if we had the version banner redirect between folders if routes are changed between versions. If this used/if we have multiple of these each one should probably be a separate function for readability. Currently nothing is handling rerouting between folders when going back to old versions.
To test look at any version <=1.10 of core on how-to-guides/logging and hover over the
Go to the latest releaselink. It should redirect to the latest version (>=1.11) and to the folder how-to-guides/monitoring--observability.