The new navigate() call in HistoryCard.svelte uses tickets/${item.ticketId} without a leading slash and no longer supports a configurable base path (previously ticketUrlPrefix + ticketPk). This may cause broken navigation depending on the router’s expectations.
What needs to be done:
- Restore support for a configurable ticket route prefix.
- Ensure the generated URL matches the app’s actual ticket detail route.
- Add a leading slash if required by the router.
The new navigate() call in HistoryCard.svelte uses tickets/${item.ticketId} without a leading slash and no longer supports a configurable base path (previously ticketUrlPrefix + ticketPk). This may cause broken navigation depending on the router’s expectations.
What needs to be done: