René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Feature]: Progressive-enhancement form actions + optimistic updates","articleBody":"**Pre-flight checklist**\n- [x] I searched existing issues and did not find a duplicate request.\n- [x] I explained the problem or use case, not just the desired API.\n\n**Problem or use case**\nbQuery forms submit via JS (`onSubmit`) only — there is no progressive-enhancement model where a form posts to a server action and works even before/without client JS, and no optimistic-update primitive for instant feedback. React 19 added function `action`/`formAction` props on `\u003cform\u003e`/`\u003cinput\u003e`/`\u003cbutton\u003e` with `useActionState`, `useFormStatus`, and `useOptimistic`; SvelteKit ships server `form actions`. bQuery, despite having both a `forms` module and a `server` module, does not connect them this way, which is a concrete gap for resilient apps.\n\n**Proposed solution**\nAdd a form-action model that binds a form to a server action (via the `server` module / file-based route actions in #149), submits as a normal POST when JS is unavailable, and progressively enhances to a fetch-based submit with pending state when JS is present. Add an optimistic-update primitive so the UI can reflect the expected result immediately and reconcile on response. Must compose with the existing validation pipeline and with sessions/CSRF from #132.\n\n**Possible API or UX shape**\n```ts\nimport { formAction, useFormStatus, optimistic } from \"@bquery/bquery/forms\";\n\n// binds to a server action; falls back to native POST without JS\nconst submit = formAction(\"/todos\", { method: \"POST\" });\n\nconst { pending } = useFormStatus(submit);\nconst list = optimistic(todos, (cur, draft) =\u003e [...cur, draft]); // instant feedback\n```\n\n**Alternatives considered**\nKeeping JS-only submit and documenting manual `fetch` patterns — leaves bQuery without the resilience and ergonomics React 19/SvelteKit now treat as standard. Building optimistic updates only in `store` — possible, but form submission is where users expect it, so the primitive should be reachable from `forms`.\n\n**Relevant area**\n`forms`\n\n**Additional context**\nDepends on `server` session/CSRF (#132) and pairs with file-based route actions (#149). This is one of the headline React-19-parity features.\n","author":{"url":"https://github.com/JosunLP","@type":"Person","name":"JosunLP"},"datePublished":"2026-06-26T21:25:33.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/140/bQuery/issues/140"}