馃摑 Description of the feature
Confirm that the full RuntimeAppState round trip is correct and complete now that every state class is server-authoritative, and for any client-side state reapplication scaffolding that remains, remove it.
The intent was for each of the individual user stories in Phase 3 to have synced back the property state to the server, so that the client-side reapplication of the cached client-side state was no longer needed and removed for that property.
In this story, we:
- verify the end to end save/load state works as expected, and
- verify that no unnecessary client-side reapplication of state remains.
Acceptance Criteria
save/load state works as expected
馃挼 Business Value
No response
馃敆 Useful links and references
No response
馃摑 Description of the feature
Confirm that the full RuntimeAppState round trip is correct and complete now that every state class is server-authoritative, and for any client-side state reapplication scaffolding that remains, remove it.
The intent was for each of the individual user stories in Phase 3 to have synced back the property state to the server, so that the client-side reapplication of the cached client-side state was no longer needed and removed for that property.
In this story, we:
Acceptance Criteria
save/load state works as expected
馃挼 Business Value
No response
馃敆 Useful links and references
No response