Add infrastructure for stage states #115
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As the app stages are more independent in the Solara version of the app than they were in the voila version, it makes more sense to store stage states separately from one another. This PR adds the basic infrastructure for getting and creating/updating stage states. The unique key for the stage states table is (student ID, story name, stage name). I've decided to go with a stage "name" rather than using the stage index - while the stage indices for the Hubble story are pretty well set at this point, future stories will obviously be more fluid as they get developed, so it will make things easier if we don't use the ordering as our key here.