fix: update condition when to display NoAvailabilityAlert when using booking code
* fix: update condition when to display NoAvailabilityAlert when using booking code
Approved-by: Michael Zetterberg
Approved-by: Arvid Norlin
Fix/tracking fixes
* fix: remove hotelInfo and paymentInfo when user reloads page on confirmation page
* fix: clean session storage item on unmount
* fix: commented out hard navigation hook
* fix: update price calculation on room ancillary in tracking
* fix: update discount calculation
* fix: add space between fns
* fix: allow useSoftNavigation to fire pageview again on same pathname
* fix: prevent bedSelection and breakfastSelection from tracking twice
Approved-by: Hrishikesh Vaipurkar
fix(SW-2501): validation trigger
* fix(SW-2501): validation trigger
On enter details, when submitting we want to trigger the validation for
the details forms for each room. This will display error messages for
the form fields with errors if they are not already displayed, so the
user knows which fields has errors.
Approved-by: Tobias Johansson
fix(LOY-235): update pagination params for getPreviousStays and getUpcomingStays
* fix(LOY-235): update pagination parameters for getPreviousStays and getUpcomingStays functions
Approved-by: Erik Tiekstra
Fix/SW-2462 room availability error
* fix: added toast error when availability fails and you get redirect to select-rate
* fix: added support for showing alert when availability error happens
* fix: rename PaymentAlert -> BookingAlert
Approved-by: Erik Tiekstra
feat: trigger validation on form upon autofill in enter details
* feat: trigger validation on form upon autofill in enter details
Approved-by: Niclas Edenvin
Ending up doing some extra things:
Consolidated booking queries: We had both cancel and cancelMany, but functionally they’re the same, only one accepts an array and the other doesn’t. Didn’t see much point in keeping the single cancel as it wasn’t used anywhere. Thus, I could rename cancelMany to be the one stop method.
remove method for API now properly supports body so we don’t have to hijack the typing in certain places
* fix(SW-2508): now sending additional params to cancel api for new contract
Approved-by: Niclas Edenvin
* fix(SW-1563): Added new IconButton component to the design system and removed Icon variant inside the Button component
* fix(SW-1563): Added buttons around clickable images and changed to design system components
* fix(SW-1563): Renamed variants to match Figma
* fix(SW-1563): Renamed AriaButton to ButtonRAC
Approved-by: Michael Zetterberg
Approved-by: Matilda Landström
fix(SW-2438): change to breakfast buffet always and replace dash with empty string
* fix(SW-2438): change to breakfast buffet always and replace dash with empty string
* fix(SW-2438): remove none from ageOfChildren
Approved-by: Tobias Johansson
Approved-by: Matilda Landström
fix(sw-2501): remove the continue buttons on enter details
This removes the continue buttons on the enter details page.
This is only that, not the refactoring of the whole enter details page with changing to one form etc. Since I just didn’t complete that refactor today I decided to do this light variant for now.
A quick explanation is that the continue buttons are removed and instead the form is submitted (meaning saving the form data to the store) on blur on the input elements IF the form is valid. If it’s invalid we change the isComplete flag in the store to false. This will hopefully also fix a bug where you were able to submit old data if the new data is invalid.
When clicking the submit button and a room is incomplete/invalid the browser scrolls to the first invalid room.
Approved-by: Erik Tiekstra
