-
Notifications
You must be signed in to change notification settings - Fork 50
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
Add Avenger Backlog Notifications #932
Add Avenger Backlog Notifications #932
Conversation
- Create Notifications module and NotificationType model - Start migration for adding notifications - No functionalities added yet only template code
notification entry
Changes: * Replaced is_enable to is_enabled for Notification Preferences * Update default is_enabled to true for Notifcation Types
`import_config` must always appear at the bottom for environment specific configurations to be applied correctly. All configurations after this line will overwrite configurations that exists in the environment specific ones.
- remove auto-generated controllers and views that are not used
If user preference has no time option, use the time_option from notification_config instead. This is so that the behaviour of these users with no preferences would always follow the default chosen by the course admin
…/Santosh3007/source-academy-backend into add-avenger-backlog-notification
…/Santosh3007/source-academy-backend into add-avenger-backlog-notification
Current nus users will have their email attribute populated based on their username. nus users are identified from the provider attribute. Future nus users will have their email attribute populated on creation ideally.
- move mailing logic to notification worker - insert into sent_notifications when email is sent out successfully
- move guard clauses to prevent unnecessary querying
|
||
<p> There is a new submission by <%= @student_name %> for <a href="/"><%= @assessment_title %></a>. Please Review and grade the <a href="/">submission </a></p> | ||
|
||
<a href="/">Unsubscribe</a> from this email topic. |
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.
Rmb to update the links!
|
||
""" | ||
|
||
# def list_sent_notifications do |
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.
would these commented out functions be used in the future?
Let us merge this first so that this can be tested on staging. The remaining issues seem to be minor, and I have created issues as above to be resolved. |
Source Academy Notifications
This is the first iteration of introducing notifications into Source Academy. Currently, this introduces two notification types:
Avenger Backlog
,Assessment Submission
and only through the email medium.In future iterations, more notifications can be included and other mediums of notifications can be explored.
Changes
Notes
notifications
table is left untouched for nownotification_configs
when new courses are insert & when new assessments are createdemail
column inusers
table usingusername
(Only for NUS users where the provider is luminus)