-
Notifications
You must be signed in to change notification settings - Fork 53
Modify versions menu to keep you on the same page #628
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
kgryte
reviewed
Jul 8, 2023
kgryte
reviewed
Jul 8, 2023
kgryte
reviewed
Jul 8, 2023
kgryte
reviewed
Jul 8, 2023
kgryte
reviewed
Jul 8, 2023
kgryte
reviewed
Jul 8, 2023
kgryte
approved these changes
Jul 8, 2023
Thanks, @steff456! Let's merge this in, and we can address any encountered issues in follow-up PRs. |
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 PR fixes #620
Extra info
I realized that we cannot guarantee that there will be a page available with the same path in the rest of versions. For example, if the function was added/removed/renamed in a later version.
If the page doesn't exist we will have an error that looks like this,
My fix was to add a head request before assigning the
href
to just verify if it is working, if it doesn't exist then it will redirect to the other version's homepage.