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

Define interface and behavior for the ICorrespondenceClient #825

Closed
3 tasks done
martinothamar opened this issue Oct 10, 2024 · 0 comments
Closed
3 tasks done

Define interface and behavior for the ICorrespondenceClient #825

martinothamar opened this issue Oct 10, 2024 · 0 comments
Assignees

Comments

@martinothamar
Copy link
Contributor

martinothamar commented Oct 10, 2024

Define an interface called ICorrespondenceClient. Consider different approaches for designing the public types to make it simple to construct Correspondence messages such as builder pattern and Value Objects/domain models

Acceptance criteria

  • There is a method using the /upload endpoint, which sends all the data as multipart formdata
  • There is a method for checking the status of a correspondence
  • It is clear from the XML docs the responsibility of producing correspondences (what does it mean to successfully post a correspondence, when do users have to handle errors, how etc)
@martinothamar martinothamar moved this to 👷 In Progress in Team Apps Oct 18, 2024
@martinothamar martinothamar added feature Label Pull requests with new features. Used when generation releasenotes and removed status/triage labels Oct 18, 2024
@RonnyB71 RonnyB71 removed the feature Label Pull requests with new features. Used when generation releasenotes label Oct 21, 2024
@danielskovli danielskovli mentioned this issue Nov 8, 2024
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants