Fix double-visits after modal form submission redirects #60
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This resolves the latter part of issue #12 where double-requests were being made to the
/success
page after a modal form submission.To replicate in the demo app:
/success
GET
requests are made to the serverHere are the relevant logs:
Note how the first
visit
properly carries theresponse.responseHTML
from the form submission redirect along to the javascript adapter:The subsequent second
visit
(which shouldn't happen) is arestore
visit:The
restore
visit was being accidentally triggered by falling through a condition in theSession
where thecurrentVisit.state
was alreadycompleted
(instead ofstarted
) since the initial visit carried theresponseHTML
and didn't need to hit the network to finish the request.