Whenever we're using the InteractsWithTurboNativeRedirects trait and we're using the redirect methods it provides, I think we'd better tweak the ->with() method chains so we could treat it like:
If the request was from a Turbo Native client, we'd redirect to the refresh route, passing the status as a query string, like /refresh_historical_location?status=Post%dcreated
This way we can read it in the mobile client whenever we're handling these special routes, so no need to flash it in the session.
If the request wasn't from a Turbo Native client, we'd flash the with calls as normal.
Whenever we're using the
InteractsWithTurboNativeRedirects
trait and we're using the redirect methods it provides, I think we'd better tweak the->with()
method chains so we could treat it like:If the request was from a Turbo Native client, we'd redirect to the
refresh
route, passing thestatus
as a query string, like/refresh_historical_location?status=Post%dcreated
This way we can read it in the mobile client whenever we're handling these special routes, so no need to flash it in the session.
If the request wasn't from a Turbo Native client, we'd flash the with calls as normal.