Form model binding and old input #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

   Verify model binding and old input against javaabu/forms

   ...

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

   c0bac9c
3. n4ff4h commented on Nov 4, 2026

   

   n4ff4h

   on Nov 4, 2026

   CollaboratorAuthor

   More actions

   Verified on next-gen (c0bac9c) against javaabu/forms HandlesDefaultAndOldValue, Select, Checkbox and Radio. src/core/binding.test.tsx has 16 cases.

   The precedence matches Blade:

   • old input, then the bound value (data_get), then default
   • Laravel's old($key, $default) returns a null old value when the key exists, and so does React
   • Select uses old input, then default, then the bound value
   • checkboxes follow only old input once there is any

   Intentional differences, listed in docs/migrating-from-blade.md:

   • Radios are selected when the bound value equals their value. Blade checks every radio of a group on a truthy scalar.
   • Grouped checkboxes get unique ids.
   • Multi-selects always submit name[].

   Docs: docs/basic-usage/model-binding.md.
4. n4ff4h

   closed this as completedon Nov 4, 2026