René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Feature]: Promote `forms` to Stable — settle the 1.13 expanded surface","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**\n`forms` is **Beta** and its surface \"significantly expanded in 1.13.0\" — new validators, combinators, field arrays, a schema builder, `bindForm`/`bindField`, scope composables, and SSR helpers all arrived roughly one minor ago. There are also documented sharp edges: `validationStrategy` defaults to `'manual'` (surprising for many users), the SSR helpers \"intentionally drop functions and `File` references,\" and `createFieldArray()` requires stable item ids. A surface this large and this new, with defaults that surprise, is not yet a stable contract.\n\n**Proposed solution**\nFreeze the `forms` public API for one minor cycle, reconsider or at least loudly document the `'manual'` validation default, document the SSR serialization boundaries (functions/`File` dropped) as guaranteed behavior with guidance, and ensure field-array id requirements are validated with clear errors. Define exit criteria: frozen surface, documented defaults and serialization boundaries, validated field-array contracts, and coverage across validators/combinators/field-arrays/SSR helpers. The progressive-enhancement action model (#140) is a parallel capability ticket.\n\n**Possible API or UX shape**\n```\n## Stability: targeting Stable in 1.15.0\nFrozen surface: createForm, bindForm, bindField, validators+combinators,\nschema builder, createFieldArray, scope composables, SSR serialize helpers\nExit criteria:\n- [ ] Public API frozen for one minor\n- [ ] validationStrategy default reviewed/clearly documented\n- [ ] SSR serialization boundaries (functions/File) documented as guaranteed\n- [ ] createFieldArray id contract validated with clear errors\n```\n\n**Alternatives considered**\nPromoting now — premature given the 1.13 expansion is barely one cycle old. Changing the `'manual'` default silently — risky for existing users; better to review deliberately and document, or change with a flagged note.\n\n**Relevant area**\n`forms`\n\n**Additional context**\n`forms` is already competitive on validation depth (rivaling React Hook Form / VeeValidate); the missing piece for parity is progressive-enhancement actions (#140). Stabilizing the data model first makes that addition safe.\n","author":{"url":"https://github.com/JosunLP","@type":"Person","name":"JosunLP"},"datePublished":"2026-06-26T21:25:30.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/139/bQuery/issues/139"}