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

Link-Redirect-fix-DocsHelp-Component #1117

Closed
wants to merge 19 commits into from

Conversation

Yashwanth1906
Copy link
Contributor

What kind of change does this PR introduce?
Change to correct wrong redirecting URLs
Issue Number:
closes: #1038

Screenshots/videos:

If relevant, did you update the documentation?

Summary

This pull request addresses an issue related to incorrect URL redirection in the JSON Schema website. Users were being redirected to incorrect or unintended pages when clicking on certain links.

Changes Made:
Corrected Redirecting URLs: Updated the wrong redirecting URLs in various components to ensure they point to the correct destinations. This change enhances navigation and provides users with access to the intended content.

Refactored JSX Components: Adjusted the formatting of JSX components to comply with the project's style guide. Specifically, I ensured that there were proper spaces before closing brackets in the JSX tags, addressing the errors raised by the reviewers.

Code Consistency: Ensured consistency in the codebase by adhering to Prettier and ESLint rules, which included correcting formatting issues to enhance code readability and maintainability.

These changes improve user experience by ensuring that links function correctly, reducing frustration caused by misdirected navigation.

Does this PR introduce a breaking change?

No

@Yashwanth1906 Yashwanth1906 requested a review from a team as a code owner November 17, 2024 07:13
Copy link

github-actions bot commented Nov 17, 2024

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
website ✅ Ready (View Log) Visit Preview 7f1f77a

Copy link

codecov bot commented Nov 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (9899bc7) to head (16f2f32).

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #1117   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           10        10           
  Lines          373       381    +8     
  Branches        94        97    +3     
=========================================
+ Hits           373       381    +8     

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

@Yashwanth1906
Copy link
Contributor Author

@DarhkVoyd This is the new pull request for this closed pull request #1046 because of some git pull rebase issues. I have written all the tests and changed all the corrections that you said in that #1046 closed pull request. Sry for closing that pull request.

Copy link
Member

@aialok aialok left a comment

Choose a reason for hiding this comment

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

LGTM. Testing part ✅️

@Yashwanth1906
Copy link
Contributor Author

@aialok Is everything fine with the pr ? Is there any one want to review it?

Copy link
Member

@DarhkVoyd DarhkVoyd left a comment

Choose a reason for hiding this comment

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

Hey, thanks for working on this. This is almost done, just a few suggestions:

  1. We can get rid of the console.log
  2. Since the prop name has been updated to fileRenderType, let's update the passed argument variable name to reflect the change. As I have suggested at one of the instances.

pages/[slug].page.tsx Outdated Show resolved Hide resolved
@Yashwanth1906
Copy link
Contributor Author

@DarhkVoyd Done with all the changes suggested.

@DarhkVoyd
Copy link
Member

@Yashwanth1906 Hey, could you please resolve the conflicts in the PR? I'll review this PR soon.

@Yashwanth1906
Copy link
Contributor Author

@DarhkVoyd ok Ill finsih this as soon as possible

@DarhkVoyd
Copy link
Member

Hey @Yashwanth1906 You don't have to close existing PR and create a new PR for each change/review, you can continue working on the same branch and PR, we'll squash merge it.

@Yashwanth1906
Copy link
Contributor Author

@DarhkVoyd ok

@Yashwanth1906
Copy link
Contributor Author

@DarhkVoyd Hi, I have tried pulling and merging the files and it resulted in mess and i added some packages and now im superconfused how to resolve this thing. Could I make another clean PR with all the tests and changes that you told in this PR.

@DarhkVoyd
Copy link
Member

@Yashwanth1906 Sure, no worries.

@Yashwanth1906 Yashwanth1906 closed this by deleting the head repository Dec 18, 2024
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: Mis-linked page (Again)
3 participants