Feature parity with @javaabu/forms #9

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

   Feature parity with @javaabu/forms

   ...

   This issue will close once commit 30d7d7b is merged into the 'main' branch.

   30d7d7b
3. n4ff4h commented on Nov 4, 2026

   

   n4ff4h

   on Nov 4, 2026

   Author

   More actions

   Done in 30d7d7b on next-gen; CI green. Every component and prop @javaabu/forms exports (from its next-gen branch) now exists in Blade. The matrix is docs/parity.md.

   Decisions:

   • Shared field options (form-group-class, thaana, auto-resize, decimals) are read from the attribute bag in Component::withAttributes() rather than added as constructor parameters to all 15 Input subclasses. Views read them through methods (groupClass(), shouldAutoResize(), decimalPlaces(), thaanaAttributes()), because Blade captures properties before withAttributes() runs.
   • Form summary defaults to false in Blade, so v1 forms render unchanged. React defaults to true; raised in Parity with javaabu/forms v2: defaults, Blade-only attributes and string keys react-forms#18 along with the Blade-only attributes and the remaining string differences.
   • String keys follow React's locale keys for everything new (previous, next, error_summary_title, select_row, no_items_*).
   • The client-side behaviours behind these attributes (Thaana keyboard, auto-resize, focus on error, the submit spinner) ship with Ship JS and CSS through javaabu/manifest #10.
4. n4ff4h

   closed this as completedon Nov 4, 2026