Skip to content

docs: fix 404 broken relative links in direct-manipulation.md - #5311

Closed
supunyasanthaofficial wants to merge 1 commit into
react:mainfrom
supunyasanthaofficial:fix/legacy-direct-manipulation-links
Closed

supunyasanthaofficial wants to merge 1 commit into
react:mainfrom
supunyasanthaofficial:fix/legacy-direct-manipulation-links

Conversation

@supunyasanthaofficial

Copy link
Copy Markdown
Contributor

Summary

Fixed broken links in docs/legacy/direct-manipulation.md that were leading to 404 pages.

The issue was caused by incorrect relative paths. Since the file is inside the legacy/ directory, links pointing to view.md were resolving to /docs/legacy/view.md instead of the actual View component documentation.

Updated both links to use ../view.md, fixing the references to onMoveShouldSetResponder and onLayout.

Applied the same fix across all versioned documentation, from version-0.77 to version-0.88.

Test Plan

  • Ran yarn build to check the documentation build.
  • Checked that the updated Markdown links resolve correctly.
  • Confirmed that no broken relative links remain.
  • ESLint checks passed.

@meta-cla meta-cla Bot added the CLA Signed label Nov 3, 2026
@Simek

Simek commented Nov 3, 2026

Copy link
Copy Markdown
Collaborator

Hey @supunyasanthaofficial, those links works on PROD and when running app locally, so there is no need to change them:

@supunyasanthaofficial

Copy link
Copy Markdown
Contributor Author

Thanks for clarifying, @Simek I noticed the 404 while navigating the files directly on GitHub's preview and assumed it broke the rendered site as well. Since Docusaurus resolves the doc ID correctly on production and local dev, I'll go ahead and close this PR.

@Simek

Simek commented Nov 3, 2026

Copy link
Copy Markdown
Collaborator

Yeah, unfortunately a lot of links would be broken when navigating on the GitHub, since Docusaurus modifies the links path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants