-
Notifications
You must be signed in to change notification settings - Fork 1
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
[MINT-2550] Data Exchange Approach Marked Complete Notification #1403
[MINT-2550] Data Exchange Approach Marked Complete Notification #1403
Conversation
…ge approach in-app notification
… to validate email templates
* feat: added feature migration, data models, gql * chore: updated sql queries * feat: several major improvements to first semi-functional data exchange approach in-app notification * chore: updated postman collection to get all notifications * chore: updated frontend gql and backend gql for user notification preferences * chore: added simple resolver helper to dispatch emails and email test to validate email templates * chore: removed resolved question * chore: Reset all frontend files to main branch as we split the frontend work to EASI-4491 * chore: reran gql gen * chore: email unit test for data exchange approach completed * chore: removed unnecessary Scan and Value methods * chore: added unit test for activity data exchange complete notification * chore: implemented resolver for data exchange approach completed notification preferences * fix: updated various test definitions to match new user account preferences spec * chore: removed outdated comment * chore: updated postman collection renaming markedCompletedBy -> markedCompleteBy * chore: converted data exchange approach complete meta to id
# Conflicts: # cmd/dbseed/main.go # cmd/test_email/main.go # pkg/email/template_service_impl.go # pkg/graph/generated/generated.go # src/gql/gen/graphql.ts
…ta_exchange_approach # Conflicts: # MINT.postman_collection.json # cmd/dbseed/main.go # cmd/test_email/main.go # pkg/email/template_service_impl.go # pkg/graph/generated/generated.go # pkg/graph/resolvers/activity.resolvers.go # pkg/graph/resolvers/added_as_collaborator_email_test.go # pkg/graph/resolvers/data_exchange_approach_helper.go # pkg/graph/resolvers/plan_collaborator_test.go # pkg/graph/resolvers/resolver_test.go # pkg/graph/resolvers/resolver_test_utilities.go # pkg/graph/resolvers/user_notification_preferences.resolvers.go # pkg/graph/schema/types/activity.graphql # pkg/models/data_exchange_approach.go # pkg/models/data_exchange_approach_completed_activity_meta.go # pkg/notifications/data_exchange_approach_completed.go # src/gql/gen/graphql.ts
# Conflicts: # pkg/graph/generated/generated.go
…:CMSgov/mint-app into feature/MINT-2720_data_exchange_approach
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.
I think the A.C. for the user being able to select which models they get a notification for isn't quite accounted for from what I can see
This should probably just follow the same pattern that we did for the "Dates Changed" email (migration here)
You could probably even just re-use/rename that type to something like MODEL_NOTIFICATION_SELECTION_TYPE
or something like that since both use the same type of dropdown.
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.
Thanks Tom, I tested your existing functionality and confirmed I received emails and notifications. I agree with Clay's note about needing to specify which models to receive notifications.
Most of the feedback I've provided is in regards to implementing some standard paradigms for store methods, and a few about data instantiation. Please let me know if you have any questions.
pkg/models/plan_data_exchange_approach_completed_activity_meta.go
Outdated
Show resolved
Hide resolved
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.
Thanks Tom, this looks good. There are just a couple things I noticed that I'd appreciate you taking a look at and responding to / or updating. Thanks!
...ies/SQL/user_account/get_notification_preferences_data_exchange_approach_marked_complete.sql
Outdated
Show resolved
Hide resolved
migrations/V177__Add_Data_Exchange_Approach_Marked_Complete_Notification.sql
Outdated
Show resolved
Hide resolved
…a_notif # Conflicts: # pkg/graph/resolvers/plan_data_exchange_approach_test.go
…nces for data Exchange
02a23ac
into
feature/MINT-2720_data_exchange
MINT-2550
Description
How to test this change
PR Author Checklist
PR Reviewer Guidelines