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.
The purpose of the persistence layer is to enable the Skip runtime to become the sole point of entry for data:
A Store concept has been added, so that a service's "InitialData" elements can be an input array as it is today, or a Store (this allows mixing requirements, with different stores for different needs depending on the nature of the data, while still having the possibility of volatile data).
A store is a class that implements the interface:
If the write in SKIP runtime fails the data is not stored, and if saving to a store fails, the corresponding write in the SKIP runtime will also fail.