Skip to content

Conversation

@ChengShi-1
Copy link
Contributor

@ChengShi-1 ChengShi-1 commented Dec 17, 2024

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:

  • send the information contacts
  • receive back from the api with details as well

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:

@ChengShi-1 ChengShi-1 added Size: 3 A percentage of a sprint. 2.1 hours. GREI Re-arch GREI re-architecture-related Original size: 3 SPA.Q4.9 Collection Page: Contact FY25 Sprint 12 FY25 Sprint 12 (2024-12-04 - 2024-12-18) labels Dec 17, 2024
@ChengShi-1 ChengShi-1 linked an issue Dec 17, 2024 that may be closed by this pull request
Copy link
Contributor

@GPortas GPortas left a 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 GPortas added the SPA.Q1 Not related to any specific Q1 feature label Jan 15, 2025
@cmbz cmbz added the FY25 Sprint 15 FY25 Sprint 15 (2025-01-15 - 2025-01-29) label Jan 15, 2025
@cmbz cmbz added the FY25 Sprint 16 FY25 Sprint 16 (2025-01-29 - 2025-02-12) label Jan 30, 2025
@ChengShi-1 ChengShi-1 removed their assignment Feb 1, 2025
@ChengShi-1 ChengShi-1 removed the Waiting label Feb 1, 2025
@ChengShi-1 ChengShi-1 requested a review from GPortas February 4, 2025 14:33
@GPortas GPortas self-assigned this Feb 10, 2025
Copy link
Contributor

@GPortas GPortas left a 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 GPortas assigned ChengShi-1 and unassigned GPortas Feb 10, 2025
@ChengShi-1
Copy link
Contributor Author

@GPortas Thanks for your reviewing and suggestions:) I made some new changes here, waiting to be reviewed again.

Copy link
Contributor

@GPortas GPortas left a 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!

@cmbz cmbz added the FY25 Sprint 17 FY25 Sprint 17 (2025-02-12 - 2025-02-26) label Feb 12, 2025
@ofahimIQSS
Copy link
Contributor

tests passing - merging PR

@ofahimIQSS ofahimIQSS merged commit 67d880f into develop Feb 14, 2025
5 checks passed
@ofahimIQSS ofahimIQSS deleted the 231-implement-use-case-for-sending-information-to-contacts branch February 14, 2025 18:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

FY25 Sprint 12 FY25 Sprint 12 (2024-12-04 - 2024-12-18) FY25 Sprint 14 FY25 Sprint 14 (2025-01-02 - 2025-01-15) FY25 Sprint 15 FY25 Sprint 15 (2025-01-15 - 2025-01-29) FY25 Sprint 16 FY25 Sprint 16 (2025-01-29 - 2025-02-12) FY25 Sprint 17 FY25 Sprint 17 (2025-02-12 - 2025-02-26) GREI Re-arch GREI re-architecture-related Original size: 3 Size: 3 A percentage of a sprint. 2.1 hours. SPA.Q1 Not related to any specific Q1 feature SPA.Q4.9 Collection Page: Contact

Projects

Status: Done 🧹

Development

Successfully merging this pull request may close these issues.

Implement use case for sending information to contacts

6 participants