Fix/SW-2290 new ui for signup on enter details page
* fix(SW-2290): New UI for join card
Approved-by: Michael Zetterberg
Approved-by: Tobias Johansson
Approved-by: Bianca Widstam
Fix/SW-2189 trigger on blur
* fix(SW-2189): do not trigger email when typing
* fix(SW-2189): use onblur on multiroom as well
Approved-by: Tobias Johansson
fix: Don't require special requests
* fix: Don't require special requests
Special requests for room one was wrongly marked as required
Approved-by: Bianca Widstam
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
feat: trigger validation on form upon autofill in enter details
* feat: trigger validation on form upon autofill in enter details
Approved-by: Niclas Edenvin
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
fix(sw-1897): show member price modal immediately
* fix(sw-1897): show member price modal immediately
* Make checkbox fully controlled
* Remove action in the store that wasn't used
Approved-by: Hrishikesh Vaipurkar
fix(sw-1867): Don't allow same name or membno between rooms
* fix(sw-1867): Don't allow same name or membno between rooms
We don't want to allow two different rooms to have the same firstname
and lastname combination or the same membership number.
* Fine tune validation triggers
* Add comments explaining manual validation triggering
* Change to react-hook-form built-in deps instead
Approved-by: Simon.Emanuelsson
* fix(SW-2247): Removed accordion like special requests block and changed button variant
* fix(SW-2247): Added additional info for bedtype selection
Approved-by: Tobias Johansson
Approved-by: Niclas Edenvin
Switches out all the old icons to new ones, and moves them to the design system. The new icons are of three different types: Materialise Symbol, Nucleo, and Customized. Also adds further mapping between facilities/amenities and icons.
Approved-by: Michael Zetterberg
Approved-by: Erik Tiekstra
fix: allow rates that only have either of member or public to be selectable
* fix: allow rates that only have either of member or public to be selectable
Approved-by: Michael Zetterberg
Migrate to a monorepo setup - step 1
* Move web to subfolder /apps/scandic-web
* Yarn + transitive deps
- Move to yarn
- design-system package removed for now since yarn doesn't
support the parameter for token (ie project currently broken)
- Add missing transitive dependencies as Yarn otherwise
prevents these imports
- VS Code doesn't pick up TS path aliases unless you open
/apps/scandic-web instead of root (will be fixed with monorepo)
* Pin framer-motion to temporarily fix typing issue
https://github.com/adobe/react-spectrum/issues/7494
* Pin zod to avoid typ error
There seems to have been a breaking change in the types
returned by zod where error is now returned as undefined
instead of missing in the type. We should just handle this
but to avoid merge conflicts just pin the dependency for
now.
* Pin react-intl version
Pin version of react-intl to avoid tiny type issue where formatMessage
does not accept a generic any more. This will be fixed in a future
commit, but to avoid merge conflicts just pin for now.
* Pin typescript version
Temporarily pin version as newer versions as stricter and results in
a type error. Will be fixed in future commit after merge.
* Setup workspaces
* Add design-system as a monorepo package
* Remove unused env var DESIGN_SYSTEM_ACCESS_TOKEN
* Fix husky for monorepo setup
* Update netlify.toml
* Add lint script to root package.json
* Add stub readme
* Fix react-intl formatMessage types
* Test netlify.toml in root
* Remove root toml
* Update netlify.toml publish path
* Remove package-lock.json
* Update build for branch/preview builds
Approved-by: Linus Flood