If a form submission redirects, the target page is rendered twice about turbo-ios

[zachwaugh]

Thanks for bringing this up. Turbo has a solution for this, but I don't think it's documented or shown in the demo. When Turbo submits a form that redirects, it will automatically follow that redirect as you noticed. It will then propose a visit to the app. That VisitProposal though will include the full response from the redirect in the proposal.options. You can pass that response to the next visit and it will use it instead of making another request. It also has the advantage of rendering immediately.

let options: VisitOptions = ... // options saved from previous visit proposal
session.visit(visitable, options: options)

I'll add an example of that to the demo project.

[ghiculescu]

Great, thanks @zachwaugh - I will give that a try once the demo's updated. I know it's probably not your domain, but do you know if the same approach will work for turbo-android?

[zachwaugh]

I believe Android works the same way, but @jayohms can confirm.

[ghiculescu]

Okay I tested that code snippet, and it seems to work well for this particular issue.

Is there ever a reason to call session.visit without the options argument? The only case I can think of is on initial boot, at which point options would be nil anyway.

[zachwaugh]

Mostly just for convenience. If you omit options, it uses the default options, which is just an advance action and no response - https://github.com/hotwired/turbo-ios/blob/main/Source/Session/Session.swift#L64.