Handle the booking cart entirely with HTMx
Besides the dynamic final cart, that was already handled by HTMx, i had
to check the maximum number of guests, whether the accommodation allows
“overflow”, whether dogs are allowed, and that the booking dates were
within the campground’s opening and closing dates.
I could do all of this with AlpineJS, but then i would have to add the
same validation to the backend, prior to accept the payment. Would not
make more sense to have them in a single place, namely the backend? With
HTMx i can do that.
However, i now have to create the form “piecemeal”, because i may not
have the whole information when the visitor arrives to the booking page,
and i still had the same problem as in commit d2858302efa—parsing the
whole form as is would leave guests and options field empty, rather than
at their minimum values.
One of the fieldsets in that booking form are the arrival and departure
dates, that are the sames we use in the campsite type’s page to
“preselect” these values. Since now are in a separate struct, i can
reuse the same type and validation logic for both pages, making my
JavaScript code useless, but requiring HTMx. I think this is a good
tradeoff, in fact.
2024-02-10 02:49:44 +00:00
|
|
|
|
<!--
|
|
|
|
|
|
SPDX-FileCopyrightText: 2023 jordi fita mas <jordi@tandem.blog>
|
|
|
|
|
|
SPDX-FileCopyrightText: 2023 Oriol Carbonell <info@oriolcarbonell.cat>
|
|
|
|
|
|
SPDX-License-Identifier: AGPL-3.0-only
|
|
|
|
|
|
-->
|
|
|
|
|
|
{{ define "title" -}}
|
|
|
|
|
|
{{( pgettext "Booking" "title" )}}
|
|
|
|
|
|
{{- end }}
|
|
|
|
|
|
|
|
|
|
|
|
{{ define "content" -}}
|
|
|
|
|
|
{{- /*gotype: dev.tandem.ws/tandem/camper/pkg/booking.publicPage*/ -}}
|
|
|
|
|
|
<h2>{{ template "title" . }}</h2>
|
2024-02-24 19:03:11 +00:00
|
|
|
|
{{ if .HasErrors -}}
|
|
|
|
|
|
<div role="alert" class="error">
|
|
|
|
|
|
<p>{{( gettext "Sorry, there was a problem. You’ll find more details highlighted below." )}}</p>
|
|
|
|
|
|
</div>
|
|
|
|
|
|
{{- end }}
|
Handle the booking cart entirely with HTMx
Besides the dynamic final cart, that was already handled by HTMx, i had
to check the maximum number of guests, whether the accommodation allows
“overflow”, whether dogs are allowed, and that the booking dates were
within the campground’s opening and closing dates.
I could do all of this with AlpineJS, but then i would have to add the
same validation to the backend, prior to accept the payment. Would not
make more sense to have them in a single place, namely the backend? With
HTMx i can do that.
However, i now have to create the form “piecemeal”, because i may not
have the whole information when the visitor arrives to the booking page,
and i still had the same problem as in commit d2858302efa—parsing the
whole form as is would leave guests and options field empty, rather than
at their minimum values.
One of the fieldsets in that booking form are the arrival and departure
dates, that are the sames we use in the campsite type’s page to
“preselect” these values. Since now are in a separate struct, i can
reuse the same type and validation logic for both pages, making my
JavaScript code useless, but requiring HTMx. I think this is a good
tradeoff, in fact.
2024-02-10 02:49:44 +00:00
|
|
|
|
<form id="booking" action="/{{ currentLocale }}/booking" method="post"
|
|
|
|
|
|
data-hx-include="this"
|
|
|
|
|
|
data-hx-target="this"
|
|
|
|
|
|
data-hx-replace-url="true"
|
|
|
|
|
|
>
|
|
|
|
|
|
{{ template "fields.gohtml" . }}
|
|
|
|
|
|
</form>
|
|
|
|
|
|
{{- end }}
|