@ -5,7 +5,7 @@ Turbo Frames (https://github.com/hotwired/turbo-rails) for form pages/questions
#### Impact on Performance
#### Impact on Performance
Using Turbo Frames allows us to swap out just the question part of the page without needing full page refreshes as you go through the form and provides an "Single Page Application like" user experience. Each question still gets a unique URL that can be navigated to directly with the Case Log ID and the overall user experience is that form navigation feels faster.
Using Turbo Frames allows us to swap out just the question part of the page without needing full page refreshes as you go through the form and provides a "Single Page Application like" user experience. Each question still gets a unique URL that can be navigated to directly with the Case Log ID and the overall user experience is that form navigation feels faster.
#### Impact on interrupted sessions
#### Impact on interrupted sessions
@ -14,6 +14,6 @@ We currently have a single Active Record model for Case Logs that contains all t
This means that when a user navigates away from the form or closes the tab etc, they can use the URL to navigate directly back to where they left off, or follow the form flow through again, and in both cases their submitted answers will still be there.
This means that when a user navigates away from the form or closes the tab etc, they can use the URL to navigate directly back to where they left off, or follow the form flow through again, and in both cases their submitted answers will still be there.
#### Impact on Performance
#### Impact on API
The API will still expect to take a JSON describing the case log, instantiate the model with the given fields, and run validations as if it had been submitted.
The API will still expect to take a JSON describing the case log, instantiate the model with the given fields, and run validations as if it had been submitted.
