Server-driven routing behaviour

[domchristie]

This stems from #130

When using server driven routing, the framework will always dismiss a modal (if present), meaning it's not possible to navigate a modal navigation stack:

• /recede_historical_location dismisses the modal and pops the main stack
• /refresh_historical_location dismisses the modal and reloads the page on the main stack
• /resume_historical_location dismisses the modal

In order to support server-driven modal navigations, how about the following:

• /pop_historical_location pops the current stack
• /reload_historical_location reloads the page on the current stack
• /resume_historical_location dismisses the modal (as before)
• /dismiss_and_pop_historical_location dismisses the modal and pops the main stack (supersedes recede)
• /dismiss_and_reload_historical_location dismisses the modal and reloads the page on the main stack (supersedes refresh)
• /recede_historical_location for backwards compatibility
• /refresh_historical_location for backwards compatibility

(reload is used because refresh is currently used)

---

Thinking about the implementation of this, it might be cool to enable "compound" presentation values like so:

{
  "rules": [
    {
      "patterns": [
        "/dismiss_and_pop_historical_location"
      ],
      "properties": {
        "presentation": "dismiss pop"
      }
    },

    {
      "patterns": [
        "/pop_and_reload_historical_location"
      ],
      "properties": {
        "presentation": "pop refresh"
      }
    }
  ]
}

This would require adding a new dismiss presentation value to dismiss a modal if present.

[joemasilotti]

Compound presentations aside, is there anything here that can't be done with custom path configuration in application code?

[MichalSznajder]

I am missing builtin clear_all_and_push. I have series of screens (eg. wizard) and at the end I need to clear all and show final summary. I have application code that does it but it is fragile (I have custom controller that does it for me)

[ibrahima]

One thing I've been wanting is the ability to conditionally do different native navigation actions in a single controller request based on the previous state.

For example, if I'm coming from a "sibling" route (same except the final identifier) I want to "replace" the current top of the navigation stack, but otherwise I want to push a new item as usual. I don't know if that's possible with path configuration or the existing server wide capabilities but if it is I haven't figured out how you would do it. I mean, I can do it if I'm going to a link from the sibling itself with data attributes. But I think what I'm trying to do is a little more unusual, because I want to use a native buttons for this navigation.

[domchristie]

I wonder if this is doable with a custom turbo stream that calls Turbo.visit with a replace action? This would sort of replicate what was possible with Turbolinks-rails: https://github.com/turbolinks/turbolinks-rails/blob/4fffc808b437936808f0888a87b1a1ae1bbcb1cd/lib/turbolinks/redirection.rb#L31

[domchristie]

But it’s probably doable with path config too if your sibling routes all have part of their url path in common

[domchristie]

No. I suppose the aim is to address confusion with the current API and enhance the out-of-the-box features.

[joemasilotti]

That's what I thought, I just wanted to make sure.