Component parity with javaabu/forms v2 #12

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 a commit that references this issue on Nov 4, 2026

   Parity with javaabu/forms v2: docs/parity.md and agreed defaults

   ...

   e8802cb
3. n4ff4h commented on Nov 4, 2026

   

   n4ff4h

   on Nov 4, 2026

   CollaboratorAuthor

   More actions

   Done on next-gen (e8802cb): docs/parity.md.

   The matrix was generated from the TypeScript props of every exported component and compared with the constructors of the Blade v2 components on forms next-gen. Then I sorted the differences into three groups: Blade attribute-bag props, named slots, and real differences. It has four parts: components, shared field attributes, per-component differences, and behaviours and strings.

   Coordinated with the forms agent in #18:

   • Form summary defaults to false in both.
   • These stay Blade-only: dateFormat, the select2 icon-picker options, jsonEncode and floating.
   • React gained Errors bag, ErrorSummary bag and Textarea wysiwyg to match Blade.
   • String keys are aligned.

   The only open point is table_array_separator (", " vs v1's ","), which is waiting on the forms agent in #18.
4. n4ff4h

   closed this as completedon Nov 4, 2026