Add back and forward support for app actions

[joey-grafana]

Fixes #34

[adrapereira]

Is manipulating the URL params manually the only option? It feels unintuitive and unsafe to me. I would guess that we can update the variables state or the scene state and let scenes automatically sync the state with the URL, propagating the changes as needed.

[joey-grafana]

Is manipulating the URL params manually the only option? It feels unintuitive and unsafe to me. I would guess that we can update the variables state or the scene state and let scenes automatically sync the state with the URL, propagating the changes as needed.

I thought it was already syncing the state with the url? I'm looking to add a historyStep and would love to have the url state handle that but I'm getting a bit confused with the differing scenes versions and the appropriate approach to accomplish this. I've seen an example in the docs of using the url-sync but also seen a comment that mentions using locationService.partial so not certain right now which approach is best.

[ifrost]

Have you tried grafana/scenes#878 (createBrowserHistorySteps)

Is manipulating the URL params manually the only option?

In explore-profiles instead of manipulating the URL we push the current one to the history. Not ideal but at least doesn't require manually building URL, but we're not on the latest scenes so cannot make use of it yet

[adrapereira]

Let's update scenes!

[adrapereira]

I'm really not a fan of manipulating the URL manually.
Can you look into these two scenes functions? These should provide a cleaner way to manage the history steps.