Detail navigation

Since wo do not want a full blown up navigation library like react-router i implemented a own navigation solution which can just navigate by updating the search param for the detail page

requested review from @OC000008353898

assigned to @OC000033413348

Since wo do not want a full blown up navigation library like react-router

I also think this is a bit of misrepresentation: I do not want to carve out a routing hole for the SPA's router in the HTTP server configuration of the CMS. I am certainly open to using a full blown SPA router here, we just need to limit the routing to happen based on the query string instead of the path.

added 1 commit

• 4c4fae92 - prefer zustan over react context

Compare with previous version

added 1 commit

• acb7e6ff - respect all query params on "isDetailPage" selector

Compare with previous version

added 1 commit

• 6fdf8566 - prettier

Compare with previous version

marked this merge request as ready

Needs a rebase to resolve conflicts. Also the useNavigation hook should get a unit test now that the testing architecture is merged.

added 2 commits

• bf9405f4 - renamed prop Link.query to Link.to
• dee4f40f - rely on useHitId instead of manual query-string checking

Compare with previous version

added 1 commit

• 0b55b876 - Merge branch 'main' into detail-navigation

Compare with previous version

added 1 commit

• eda87f67 - rely on window.URL instead of raw href string

Compare with previous version

added 1 commit

• 4ab88202 - made useNavigation hook aware of other search params

Compare with previous version