Niclas Edenvin 0ac09f37f6 Merged in fix/sw-1177-search-history (pull request #1124)
fix(SW-1177): fix localization problems in search history

* fix(SW-1177): fix localization problems in search history

When saving search history the whole location objects where stored and
also used later. This made the list display in different languages if
the user previously had search for something in another language.
Another issue where that the list where also deduped based on name of
the search item, which meant that there could be multiple history
items for the same entity and the same ID, e.g. `Gothenburg` and
`Göteborg`.


Approved-by: Bianca Widstam
2025-01-07 10:32:32 +00:00
2024-04-16 11:36:53 +02:00
2024-09-03 14:15:48 +02:00
2024-12-20 11:04:46 +01:00
2025-01-02 13:46:51 +01:00
2024-12-20 09:28:06 +01:00
2024-12-20 09:28:06 +01:00
2025-01-02 13:46:51 +01:00
2024-02-29 17:52:29 +01:00
2024-11-21 07:25:38 +01:00
2024-01-09 15:48:28 +01:00

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

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Inter, a custom Google Font.

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!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.

Description
No description provided
Readme 81 MiB
Languages
TypeScript 90.4%
CSS 7.5%
JavaScript 1.9%