-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature submissions store #1443
Conversation
451e351
to
0a5b4f5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just note that one comment 😄
return JSON.stringify(object); | ||
} | ||
|
||
_keyFor(exerciseId) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok! Just take into account that this may conflict in the future with organization-separated progress.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And here we go 7 months since this comment https://github.com/mumuki/mumuki-laboratory/pull/1593/files#diff-7d5ce0a5557f3df2e8224d66906a9fc203f52f5a6a356f583361a95a5f9f78d8R97 @luchotc
🎯 Goal
This PR introduces the
SubmissionsStore
, a JS repository for user progress that replaced the one-variable last-submission cache.This has two consequences:
This API is not yet stable, and I may change in the near future, but is consistent enough to merging into main branch and start using it.
📝 Details
currentExerciseId
🔜 Future work
More tests and documentation will be added when this API is stabilized.
🔙 Backward compatibility
This PR is not backward compatible
👀 See also