Sections, repeating groups, wizards, cascading and conditional inputs #6

Activity

1. n4ff4h

   added

   next-genNext-gen Javaabu packagesNext-gen Javaabu packages

   featurePackage feature from the specPackage feature from the spec

   on Nov 4, 2026
2. n4ff4h

   added 3 commits that reference this issue on Nov 5, 2026

   Form definitions, versions, entries and the stencil compiler

   ...

   6490efd

   Inertia React pages, stencil components for repeaters and content, JS…

   ...

   322b443

   Wizard rendering test; an input type with its own stencil field and R…

   ...

   7cb7ca9
3. n4ff4h commented on Nov 5, 2026

   

   n4ff4h

   on Nov 5, 2026

   CollaboratorAuthor

   More actions

   Done. Everything compiles to stencil, so it works the same in Blade and React and is checked on the server:

   • Sections and wizards. Sections become stencil Section; with the wizard layout they become Wizard/Step.
   • Conditions. in, not_in, checked and not_checked on sections and fields (AND), compiled to stencil's declarative conditions.
   • Cascading selects. They use @javaabu/forms' select2 cascade, fed by an options endpoint on both route groups, or by any URL. The server checks that the value belongs to the parent's value.
   • Repeating groups. This is the Javaabu\FormBuilder\Stencil\Repeater stencil field. It handles per-row rules, attributes, conditions on siblings and dehydration, and renders with a Blade view plus script and a React component. Upstreaming is proposed in Proposal: a Repeater field (repeating groups), implemented in javaabu/form-builder stencil#18 (not blocking).

   Docs: docs/basic-usage/structure.md
4. n4ff4h

   closed this as completedon Nov 5, 2026