Fix user progress database bug
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Student progress data is stored in the "progress" variable in the database. Because a listener is placed on this document for every user, each time a student updates his/her progress, a read is processed to every other student causing unneeded database reads. Need to move progress to a new collection or sub collection to fix this bug.
- [ ] Add progress collection / sub collection to store user progress data
- [ ] Set user dashboard to read initial progress data from new collection
- [ ] set user dashboard to update user progress to new location
- [ ] set admin dashboard to add new snapshot listener for progress data
- [ ] set admin dashboard to create progress document in new collection on workshop creation.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.