Files
web/apps/scandic-web
Joakim Jäderberg 68cd061c6d Merged in feature/select-rate-vertical-data-flow (pull request #2535)
Feature/select rate vertical data flow

* add fix from SW-2666

* use translations for room packages

* move types to it's own file

* Merge branch 'master' of bitbucket.org:scandic-swap/web into feature/select-rate-vertical-data-flow

* merge

* feature/select-rate: double rate for campaing rates

* revert NODE_ENV check in Cookiebot script

* revert testing values

* fix(SW-3171): fix all filter selected in price details

* fix(SW-3166): multiroom anchoring when changing filter

* fix(SW-3172): check hotelType, show correct breakfast message

* Merge branch 'feature/select-rate-vertical-data-flow' of bitbucket.org:scandic-swap/web into feature/select-rate-vertical-data-flow

* fix: show special needs icons for subsequent roomTypes SW-3167

* fix: Display strike through text when logged in SW-3168

* fix: Reinstate the scrollToView behaviour when selecting a rate SW-3169

* merge

* .

* PR fixes

* fix: don't return notFound()

* .

* always include defaults for room packages

* merge

* merge

* merge

* Remove floating h1 for new select-rate


Approved-by: Anton Gunnarsson
2025-08-13 12:45:40 +00:00
..
2025-05-22 14:00:38 +02:00
2025-04-07 12:17:35 +02:00

This is a Next.js project bootstrapped with create-next-app.

Getting Started

  • Firt, make sure you have built the design-system once:
yarn workspace @scandic-hotels/design-system build
  • Create a .env.local file in the root of the scandic-web directory with the keys from the .env.example file.

  • 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

Icons / Material Symbols

Read the README.md in the monorepo root.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!