Create notification DB layer for v9 migration #12074
Closed
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
…stion edits (TEAMMATES#12030) * Add FeedbackSessionPublishStatus enum to instructor session edit page * Add session publish status as a check for warning message when editing questions * Update snapshot testing for question edit form and session edit page --------- Co-authored-by: wuqirui <53338059+hhdqirui@users.noreply.github.com>
…ch (TEAMMATES#12066) * Fix rubric stats calculation * Fix tests
…om/hhdqirui/teammates into v9-migration-notification-db-layer
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.
Part of #12048
Create notification DB layer with CRUD. Minor update to notification sql entity to fix the wrong implementation.