Files
web/apps/scandic-web
Chuma Mcphoy (We Ahead) 56d5ad77d1 Merged in fix/SW-2068-correct-public-url-from-my-stays-overview-page (pull request #1694)
feat(SW-2068): Link to Correct Public URL from within My Stays Overview Page

* feat(SW-2068): Link to Correct Public URL from within My Stays Overview Page

- Added language parameter to previous and upcoming stays queries.
- Updated Client components to utilize the new language hook.
- Refactored EmptyUpcomingStays component to dynamically generate links based on the current language.
- Adjusted user input validation to include optional language parameter.

* refactor(SW-2068): Update EmptyUpcomingStays components to use PUBLIC_URL + add utility to handle TLD based on language

* chore(SW-2068): Clarify TLD

* feat(SW-2068): documentation for getTldForLanguage

* refactor(SW-2068): Simplify booking URL construction in updateStaysBookingUrl

* refactor(SW-2068): Remove incorrect TLD update logic from booking URL construction

* refactor(SW-2068): Centralize booking URL paths using myBookingPath constant

* refactor(SW-2068): Streamline search params in booking URL construction logic in updateStaysBookingUrl


Approved-by: Christian Andolf
2025-04-02 12:44:02 +00:00
..
2025-03-26 09:55:26 +01: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

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!