numerus/web/template
jordi fita mas f93d557aa9 Move the multiselect “component” to the select-field template
I had in the product edit page only because it was easier to test there
while i was developing it, but it is something that should be done for
all select[multiple], of course.

I removed the whole x-cloak thing because i am not sure what would
happen if i do something wrong and Alpine can not initialize the
multiselect; probably show nothing to the user.  Now it shows the
native select a fraction of a second, but if i fuck it up at least the
user can still use the app.
2023-03-15 11:44:18 +01:00
..
contacts Add products section 2023-02-04 11:32:39 +01:00
invoices Add the edit form for invoices 2023-03-13 15:00:35 +01:00
products Move the multiselect “component” to the select-field template 2023-03-15 11:44:18 +01:00
app.gohtml Move the multiselect “component” to the select-field template 2023-03-15 11:44:18 +01:00
dashboard.gohtml Move page titles to their respective templates 2023-01-31 13:07:17 +01:00
form.gohtml Move the multiselect “component” to the select-field template 2023-03-15 11:44:18 +01:00
login.gohtml Use a “proper” struct for the login form 2023-02-01 11:02:32 +01:00
profile.gohtml Add breadcrumbs 2023-02-03 13:58:10 +01:00
tax-details.gohtml Add the payment method relation and corresponding form 2023-03-03 16:49:06 +01:00
web.gohtml Add custom function to get the current locale from templates 2023-01-31 15:45:51 +01:00