solid-docs

Before: the router data page presented a mutation as a . Calling a server function from code came later, as a side note. The guides also used "action" loosely for the router's wrapper and still mentioned the deprecated and . The generated reference was behind solid . After: Data loading and mutations** starts with "Mutate with a server function". That section is a server function called inside a core , and the mounted router applies its , and single-flight data. It covers optimistic writes before the and catching the rejected . Next comes "Add a form with ", which covers what a `aria-busyuseSubmissions.onSubmit.with()nextcreateDeferredServerFunctionsSendconfigureServerFunctionsClientX-Revalidatecheck-examples` against solid, router, meta and vite-plugin checkouts reports 0 errors in 584 blocks, and the tone lint reports no errors. 🤖 Generated with Claude Code https://claude.ai/code/session_01CLHVghj7oAvSMqnq9WRKdv

Before: the 2.0 docs teach the router's and . They also say a server function called directly from an event handler doesn't revalidate, and that the router's single flight is installed by the first action. After (matching @solidjs/router 2.0.0-next.41, solidjs/solid-router#688): The router's is documented as ( becomes ). The old names are covered as deprecated aliases in the reference and the migration guide. is deprecated. Pages now call the server function directly, and the durable-generation chat example drops it. A mounted router applies revalidation, redirects and flight data on any server function call. Every POST is treated as a mutation and revalidates the queries on screen. Reads through and are exempt, and opts a non-mutation out. The troubleshooting entry that blamed direct calls is rewritten, and the integrate-a-router page no longer describes the old action-gated rendezvous. Core solid-js usages are unchanged. This touches 17 pages: router data and its reference/types/index, server functions (mutations and responses, progressive enhancement, durable generation, index), forms, protected routes, the from-solid-router migration, integrate a router, server rendering, the overview, data-fetching patterns and the glossary. Validation: checks 1346 blocks and passes for every changed page. Its 5 errors are all in unchanged pages and come from the older npm meta package being missing / exports. passes on the changed files. reports 0 errors. _Generated by Claude Code_

📝 Issue Description redirects three old URLs to pages that no longer exist, so each one ends on the 404 page: The router pages moved under , and the reference page is now , but the redirect table was not updated. (without the trailing slash) also returns 404. 📋 On which page(s) it occurs https://docs.solidjs.com/references/api-reference/reactive-utilities/on https://docs.solidjs.com/routing/migration/ https://docs.solidjs.com/routing/migration https://docs.solidjs.com/guides/how-to-guides/routing-in-solid/solid-router 🤔 Expected Behavior Each old URL redirects to the current page for that content. 👀 Current Behavior The other two URLs behave the same way. 🖥️ Browser Any (reproduced with curl). 📄 Additional Information All other entries in the redirect table resolve to existing pages.