feat: Migrate ranger docs to v2 layout

[lachlancollins]

Uses new v2 docs layout and logic

See also: TanStack/ranger#85

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
tanstack-com	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 25, 2024 9:22pm

[fulopkovacs]

I get an error for ranger doc routes where version is not v0 or latest. The error message says that selectedOption is undefined.

See these routes for example:

• localhost:3000/ranger/v1/docs/overview
• localhost:3000/ranger/v8/docs/overview

(I am on the docs-rework branch from #153 in my local clone of the tanstack/ranger repo.)

[lachlancollins]

I get an error for ranger doc routes where version is not v0 or latest. The error message says that selectedOption is undefined.

See these routes for example:

• localhost:3000/ranger/v1/docs/overview
• localhost:3000/ranger/v8/docs/overview

I think this is a development-only problem, with a different issue in production. Since local development uses the file system, the version selector doesn't work (different git branches). If you delete the fetchFs function from fetchRepoFile in a project with the v2 layout, it instead returns something like this:

This is for http://localhost:3000/table/v9/docs/introduction

For now, I'm just going to change the 'latest' branch back to v1, but this will require a general fix for the new docs layout, rather than a specific fix for ranger.

I'd imagine the fix would be something like checking if $version was a valid entry in availableVersions, and if not redirecting to latest.

[lachlancollins]

I'd imagine the fix would be something like checking if $version was a valid entry in availableVersions, and if not redirecting to latest.

This was an incredibly quick fix to implement :)

[fulopkovacs]

Awesome, works perfectly! ☺️ 🚀