-
Notifications
You must be signed in to change notification settings - Fork 10
implement use case for sending information to contacts #232
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
implement use case for sending information to contacts #232
Conversation
GPortas
left a comment
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.
The design, layering, and approach are correct, but we should use a different API endpoint for the reasons I mentioned in one of my comments. If there isn't an alternative endpoint in the API, we will need to implement one.
GPortas
left a comment
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.
Looks good! @ChengShi-1
I've added minor suggestions. I think we should always use email addresses under our control for testing, to avoid potential side effects.
|
@GPortas Thanks for your reviewing and suggestions:) I made some new changes here, waiting to be reviewed again. |
GPortas
left a comment
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.
Looks good to me. Approving!
|
tests passing - merging PR |
What this PR does / why we need it:
Implement the use case allowing users to send feedback to contacts of collection or dataset.
The use case should:
Which issue(s) this PR closes:
Related Dataverse PRs:
Special notes for your reviewer:
Suggestions on how to test this:
visually inspect and run tests on it
Is there a release notes update needed for this change?:
Additional documentation: