ac493fe325
Feat/SW-1149 handle status polling * feat(SW-1149): move terms and conditions sections to separate component and added copy * feat(SW-1149): Added client component to handle success callback for payment flow * fix: check for bookingCompleted status as well * feat(SW-1587): use alert instead of toast for showing payment errors * fix: added enum for payment callback status * fix: proper way of checking for multiple statuses * fix: update schema type * fix: use localised link to customer service * fix: update to use enum for status strings Approved-by: Arvid Norlin
This is a Next.js project bootstrapped with create-next-app.
Getting Started
- Firt, make sure you have built the
design-systemonce:
yarn workspace @scandic-hotels/design-system build
-
Create a
.env.localfile in the root of thescandic-webdirectory with the keys from the.env.examplefile. -
Then run the development server:
yarn dev
Open http://localhost:3000 with your browser to see the result.
Caching
You have the choice to either use redis (via redis-api; a tiny http proxy) or in-memory/unstable_cache (depending on edge or node).
Setting REDIS_API_HOST will configure it to use the distributed cache, not providing it will fall back to in-memory/unstable_cache
When pointing to the azure hosted variant you also need to provide REDIS_API_KEY
Locally it's easiest is to spin everything up using docker/podman - podman compose up or docker-compose up
This will also spin up Redis Insight so that you can debug the cache.
- Navigate to
http://localhost:5540 - Click 'Add Redis database'
- Provide Connection URL
redis://redis:6379
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!