Suggestion: 'strict' mode for state restoration #73
Labels
priority:medium
This issue has a medium priority
type:enhancement
A proposed enhancement to the api or behavior
type:feature
New feature
Milestone
State saving is tricky to get right, and if it crashes it will only do so upon state restoration at runtime, apart from writing tests.
When in debug mode however, the app could be executed in 'strict' mode to catch these kinds of errors quickly. For example, on each Scene change the entire Navigator could be saved and restored in some secondary process to ensure the application doesn't crash.
The text was updated successfully, but these errors were encountered: