🚸 tab selection and state should be reflected in URL

[jdhoffa]

The currently selected tab and its state (e.g., selections within the tab) are not reflected in the URL. This makes it impossible to return to a specific view within the dashboard. While this is a "nice-to-have" feature, it will become more critical once sharing functionality is added to the web app.

[cjyetman]

The "easy" way (at least on a simplistic website with no svelte-like fanciness) to do this would be to create separate pages for each tab and have each tab link to the appropriate page. I doubt that's desirable here.

Maybe something like this could be achieved with cookies, but I doubt that's adequate here because I suspect this issue is implicitly connected to a desire to be able to share the URL with someone else or another browser.

Alternatively, we'd need to encode the information needed to bring the user back to a specific view in the URL. That can be done through URL query string/parameters, e.g. https://rmi-pacta.github.io/pacta-dashboard-svelte?page=company-level, or possibly through a customized route or page slug if svelte can handle that, e.g. https://rmi-pacta.github.io/pacta-dashboard-svelte/company-level. One could probably hack something together with anchor tags too, e.g. https://rmi-pacta.github.io/pacta-dashboard-svelte/#company-level, though I don't think that's standard usage.

If the intent is to capture not only what tab the user is on but also what selections have been made on the various selectors on the page, I'd imagine URL query strings would be the most realistic, e.g. https://rmi-pacta.github.io/pacta-dashboard-svelte?page=company&sector=Automotive&scenario=NZE_2050, because it's easy to mix and match different key-value pairs and the order is (or at least can be) irrelevant.