Skip to content
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

[EASI-3945] Collaborator Added notification BE #1003

Conversation

StevenWadeOddball
Copy link
Contributor

@StevenWadeOddball StevenWadeOddball commented Mar 12, 2024

EASI-3945

Changes and Description

  • New added as collaborator notification type
  • Plan Collaborator Get by ID data loader
  • Plan Collaborator general refactoring for naming consistency
  • Plan Collaborator SQL files moved to sql queries package

How to test this change

  1. Bring up the application (The steps below can use either the postman collection or the FE)
  2. Add yourself as a collaborator to a model plan.
  3. Verify that you got an email in mail catcher
  4. Use Postman to view the new notification type

If desired, update your notification preferences to turn off email for added as collaborator.
5. Repeat the above steps, but confirm you don't get an email for being added as a collaborator
6. Create a new model plan, ensure you don't get notified that you were added as a collaborator.

PR Author Review Checklist

  • Met the ticket's acceptance criteria, or will meet them in a subsequent PR.
  • Added or updated tests for backend resolvers or other functions as needed.
  • Added or updated client tests for new components, parent components, functions, or e2e tests as necessary.
  • Updated the Postman Collection if necessary.

PR Reviewer Guidelines

  • It's best to pull the branch locally and test it, rather than just looking at the code online!
  • Check that all code is adequately covered by tests - if it isn't feel free to suggest the addition of tests.
  • Always make comments, even if it's minor, or if you don't understand why something was done.

…not (instead of inferrring from email service)
@StevenWadeOddball StevenWadeOddball marked this pull request as ready for review March 12, 2024 20:41
@StevenWadeOddball StevenWadeOddball requested review from a team as code owners March 12, 2024 20:41
@StevenWadeOddball StevenWadeOddball requested review from OddTomBrooks and garyjzhao and removed request for a team March 12, 2024 20:41
@StevenWadeOddball StevenWadeOddball changed the title Collaborator Added notification BE [EASI-3945] Collaborator Added notification BE Mar 14, 2024
@StevenWadeOddball StevenWadeOddball merged commit 481c065 into feature/EASI-3945_collaborator_added_notification Mar 15, 2024
12 checks passed
@StevenWadeOddball StevenWadeOddball deleted the task/EASI-3945_collaborator_added_notification_be branch March 15, 2024 13:55
garyjzhao pushed a commit that referenced this pull request Apr 2, 2024
* feat: user notification user userIDRelation

* feat: preliminary added as a collaboorator meta data type

* feat: ActivityAddedAsCollaboratorCreate and unit test

* feat: preliminary connection of added as collaborator notification

* feat: add parameter to create collaborator to send a notification or not (instead of inferrring from email service)

* feat: assert that a notification is made in the collaborator unit test

* feat: add a unit test to assert a notification is not created when sendNotification is false

* feat: new data loader WIP, collaborator sql files moved to SQL queries

* feat: standardize collaborator method naming conventions

* feat: plan collaborator get now utilizes dataloader. Correct wiring for dataloader

* feat: unit test for planCollaborator by ID data loader

* feat: utility error handling function for data loaders

* chore: remove irrelevant comment

* feat: update seeder to use config context instead of background, so it has access to data loaders

* feat: update postman collection with example of new notification type

* feat: move audit.change to be the last table truncated to address constraint issue in unit tests

* feat: incorporate truncate logic from the daily digest notification branch

* feat: add comments to the embedded SQL files for plan collaborator

* chore: correct embed statement capitalization
garyjzhao added a commit that referenced this pull request Apr 5, 2024
* [EASI-3945] Collaborator Added notification BE (#1003)

* feat: user notification user userIDRelation

* feat: preliminary added as a collaboorator meta data type

* feat: ActivityAddedAsCollaboratorCreate and unit test

* feat: preliminary connection of added as collaborator notification

* feat: add parameter to create collaborator to send a notification or not (instead of inferrring from email service)

* feat: assert that a notification is made in the collaborator unit test

* feat: add a unit test to assert a notification is not created when sendNotification is false

* feat: new data loader WIP, collaborator sql files moved to SQL queries

* feat: standardize collaborator method naming conventions

* feat: plan collaborator get now utilizes dataloader. Correct wiring for dataloader

* feat: unit test for planCollaborator by ID data loader

* feat: utility error handling function for data loaders

* chore: remove irrelevant comment

* feat: update seeder to use config context instead of background, so it has access to data loaders

* feat: update postman collection with example of new notification type

* feat: move audit.change to be the last table truncated to address constraint issue in unit tests

* feat: incorporate truncate logic from the daily digest notification branch

* feat: add comments to the embedded SQL files for plan collaborator

* chore: correct embed statement capitalization

* feat: reintroduce functionality removed in merge

* [EASI-3926] Frontend work for Add Collaborator Notification (#1031)

* updated GetNotifications

* streamline the query for add collab notification

* drying up the click hander

* move some functions around

* DRYing up the functions

* remove only in e2e test

* add test to add collaborator notification

---------

Co-authored-by: Steven Wade <[email protected]>
Co-authored-by: Steven Wade <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants