Location inputs #4

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

   Admin pages, route macros, policies and permissions for every locatio…

   ...

   90b2457

   Inertia React pages and React location selects

   ...

   01ba991

   Blade location selects, cascading country → atoll → island

   ...

   88b8f73
3. n4ff4h commented on Nov 5, 2026

   

   n4ff4h

   on Nov 5, 2026

   CollaboratorAuthor

   More actions

   Done. Country, state, city, atoll and island selects for all three:

   • Blade: <x-locations::*-select>, with parent/child/filters.
   • React: CountrySelect … IslandSelect from @javaabu/locations, with parent, filters and LocationsProvider.
   • Stencil: Stencil\\*Select::make()->dependsOn()->filters().

   Decisions:

   • Cascades: they use javaabu/forms' and @javaabu/forms' own select2 cascade (child + ajax-url + filter-field), loading from a read-only endpoint, Route::locationOptions(). No package script.
   • Country → atoll: an atoll select depending on a country lists every atoll for the Maldives and none otherwise, so forms' fallback can swap in a text field for foreign addresses.
   • Labels: options are labelled in the request's locale (HA. Haa Alifu / ހއ. ހާ އަލިފު).
   • Malé City: it has no Thaana code, so it's labelled just Malé City.

   Docs: docs/basic-usage/location-selects.md, docs/advanced-usage/options-endpoint.md.
4. n4ff4h

   closed this as completedon Nov 5, 2026