Repository navigation
[Navigation] Replace invalid 'href' prop with 'to' in Gatsby Link components - #8350
Conversation
…k components Signed-off-by: Ayush <ayushdungarwal3445@gmail.com>
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
marblom007
left a comment
There was a problem hiding this comment.
Approved. Checked against #8349: all 13 href props on Gatsby Link components are now to, each touched file imports Link from gatsby, and the TwoColLayout image link now points to /solutions/orchestration-management, matching the adjacent Learn more link. Build, DCO, triage, and CodeRabbit checks are green. Thanks for the fix.
|
Preview deployment for PR #8350 removed. This PR preview was automatically pruned because we keep only the 3 most recently updated previews on GitHub Pages to stay within deployment size limits. If needed, push a new commit to this PR to generate a fresh preview. |
Description
This PR fixes #8349
In multiple diagram and feature sections, Gatsby's
<Link>component was used withhref="..."instead of the requiredto="..."prop. In Gatsby,<Link>expectsto, and passinghrefleavestoundefined, triggering React prop type warnings and disabling Gatsby client-side route prefetching and SPA navigation.This PR updates all 13 occurrences across 6 feature sections to use
to="..."instead ofhref="...".Additionally, in
src/components/Features/TwoColLayout.js, the image card link is updated to point directly to the canonical route/solutions/orchestration-management(matching the adjacent "Learn more" link).Notes for Reviewers
hreftotoon Gatsby<Link>elements.TwoColLayout.jsto/solutions/orchestration-management.Signed commits
Summary by CodeRabbit