Turbo Native Specific Routes

I’ve noticed that the turbo-rails gem has some Native-specific routes defined (here and here), but I haven’t found any documentation on how to use them in the Turbo Native adapters (besides some tests in the Turbo Android lib - here and here).

I’m wondering how these routes should be used by the Native adapters. I’m guessing they would need to be registered in the configuration.json and checked somehow on each screen (where it makes sense), if the page is leaving the fragment but the route matches any of these refresh, recede, or resume routes, then the visit should be cancelled and the proper action taken. I guess something like the “Navigate to Destinations” documentation here), although those specifically mention web links and not form redirects (but I guess it works).

Does anyone know more about these?

1 Like