Simulator snapshots

[eladcon]

Feature Spec

The simulator can now import and export snapshots of it's current state. A snapshot describes the state of every resource in the simulator, allowing users to save their data and load it at a later point.

Some use cases that might be interesting with this feature:

• Starting from a predefined state when developing locally with the console -
  • on every simulator stop and start (e.g. code change) load a specific/last known state
  • by the user through the console UI.
• Time machine in the console - allowing to "travel" between traces and states to debug certain resources.
• Testing - allow users to start the test from a specified snapshot or assert their state of the app matches a specific snapshot (e.g. assert.matchesSnapshot(simulator.snapshot()))

Use Cases

see above

Implementation Notes

Resources can implement serialize and deserialize operations to import and export state, while the simulator calls the relevant operation on every resource.

Component

No response

Community Notes

• Please vote by adding a 👍 reaction to the issue to help us prioritize.
• If you are interested to work on this issue, please leave a comment.
• If this issue is labeled needs-discussion, it means the spec has not been finalized yet. Please reach out on the #dev channel in the Wing Slack.

[github-actions[bot]]

Hi,

This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!