René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Feature]: Promote `view` to Stable — freeze the directive contract after the 1.14 additions","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`view` is the declarative rendering layer and is still **Beta**, despite being central to authoring. Its directive contract changed materially just one minor ago: 1.14.0 added `bq-once`, `bq-init`, `bq-pre`, `bq-cloak`, `bq-html-safe`, and `bq-memo`, plus a full `bq-on` modifier system. Known rough edges remain (e.g., `bq-for` duplicate-key fallback warnings and object-expression parsing edge cases). A templating contract that just grew and still has parsing edge cases is not yet a stable foundation.\n\n**Proposed solution**\nFreeze the directive set and its expression grammar for at least one minor cycle, resolve the documented edge cases (duplicate-key handling in `bq-for`, object-expression parsing), and publish a complete, versioned directive reference with the SSR support status of each directive (coordinating with #128). Define `view` exit criteria: frozen directives, documented grammar, resolved parser edge cases, and full SSR/client behavior parity documented per directive.\n\n**Possible API or UX shape**\n```\n## Stability: targeting Stable in 1.15.0\nFrozen directives: bq-text, bq-html, bq-html-safe, bq-if, bq-show, bq-for,\nbq-class, bq-style, bq-bind:*, bq-model, bq-on(+modifiers), bq-once, bq-init,\nbq-pre, bq-cloak, bq-memo\nExit criteria:\n- [ ] Directive set + expression grammar frozen for one minor\n- [ ] bq-for duplicate-key + object-expression edge cases resolved\n- [ ] Per-directive SSR support documented (#128)\n```\n\n**Alternatives considered**\nPromoting `view` while parser edge cases remain — risks shipping a \"stable\" surface that still surprises users. Continuing to add directives before freezing — fine for Beta, but it must stop for one cycle to earn Stable.\n\n**Relevant area**\n`view`\n\n**Additional context**\nThe declarative transitions in #137 and the optional compiled path in #138 are `view` enhancements that can land before or after promotion; this ticket is specifically the freeze-and-stabilize tracking issue.\n","author":{"url":"https://github.com/JosunLP","@type":"Person","name":"JosunLP"},"datePublished":"2026-06-26T21:25:21.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/136/bQuery/issues/136"}