Skip to content
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

fix: Update Go Back button URL on implementers page #1517

Conversation

Priyanshuthapliyal2005
Copy link
Contributor

What kind of change does this PR introduce?

Fixed the "Go Back" button navigation on the implementers page by updating the URL from /guides to /learn/guides.

Changes

  • Updated prevURL prop in pages/implementers/index.page.tsx to point to the correct guides page location

Testing

  1. Go to the Implementers page
  2. Click on the "Go Back" button
  3. Verify that it correctly navigates to the guides page at /learn/guides

Issue Number:

Screenshots/videos:

gobackworking.mp4

If relevant, did you update the documentation?

Summary

The "Go Back" button on the Implementers page was navigating to an incorrect URL (/guides), resulting in a 404 error. This PR fixes the navigation by updating the URL to the correct path (/learn/guides).

This change ensures users can properly navigate back from the Implementers page to the Guides section, improving the overall navigation experience of the documentation.

Does this PR introduce a breaking change?
no

@Priyanshuthapliyal2005 Priyanshuthapliyal2005 requested a review from a team as a code owner March 14, 2025 12:17
Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Welcome to the JSON Schema Community. Thanks a lot for creating your first pull request!! 🎉🎉 We are so excited you are here! We hope this is only the first of many! For more details check out README.md file.

Copy link

github-actions bot commented Mar 14, 2025

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
website ✅ Ready (View Log) Visit Preview 72d9939

Copy link

codecov bot commented Mar 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (219521e) to head (72d9939).
Report is 16 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #1517   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           10        10           
  Lines          396       396           
  Branches       106       106           
=========================================
  Hits           396       396           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@idanidan29
Copy link
Contributor

idanidan29 commented Mar 15, 2025

@Priyanshuthapliyal2005 The issue hasn't been approved yet and is not assigned to you. Please check the contribution guidelines and please close the PR to make it easier for the maintainers.

@Priyanshuthapliyal2005
Copy link
Contributor Author

@Priyanshuthapliyal2005 The issue hasn't been approved yet and is not assigned to you. Please check the contribution guidelines and please close the PR to make it easier for the maintainers.

Thank you for your feedback. I've reviewed the contribution guidelines and couldn't find any explicit requirement about needing issue approval before submitting a PR. If there's a specific guideline I missed, please let me know and I'll be happy to adjust accordingly.

@idanidan29
Copy link
Contributor

idanidan29 commented Mar 15, 2025

@Priyanshuthapliyal2005, it's mentioned in the PR format and the guidelines that an issue can only be worked on after being released from triage. I made this mistake myself, so I thought it would be helpful to let you know, as a lot of the maintainers time is spent closing PRs for issues that are still in triage.

@Priyanshuthapliyal2005
Copy link
Contributor Author

Priyanshuthapliyal2005 commented Mar 15, 2025

@Priyanshuthapliyal2005, it's mentioned in the PR format and the guidelines that an issue can only be worked on after being released from triage. I made this mistake myself, so I thought it would be helpful to let you know, as a lot of the maintainers time is spent closing PRs for issues that are still in triage.

Thank you for the heads up! I’d appreciate it if you could share a screenshot where this is mentioned in the guidelines. Once confirmed, I will close this PR. 😊

Copy link
Collaborator

@benjagm benjagm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@benjagm benjagm merged commit 8f57573 into json-schema-org:main Mar 16, 2025
11 checks passed
Copy link

Congratulations, @Priyanshuthapliyal2005 for your first pull request merge in this repository! 🎉🎉. Thanks for your contribution to JSON Schema!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

🐛 Bug: "Go Back" Button on Implementers Page Navigates to Wrong Address (404 Error)
3 participants