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.

Sign up for GitHub

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

Jump to bottom

Migrate to RFC 9457 Problem Details for Consistent Error Responses #149

Closed
thisdudkin opened this issue Aug 30, 2024 · 2 comments
Closed

Migrate to RFC 9457 Problem Details for Consistent Error Responses #149

thisdudkin opened this issue Aug 30, 2024 · 2 comments
Labels
enhancement help wanted

Comments

@thisdudkin
Copy link
Contributor

Following the feedback on PR #146, there's an opportunity to enhance our API's error handling by adopting the RFC 9457 Problem Details for HTTP APIs specification.

This update will ensure that our API is not just functional but also robust, modern, and easy to work with.
This was referenced Nov 19, 2024
Closed
Closed
Merged
arey pushed a commit that referenced this issue Dec 28, 2024
@joaobertholino
Implements the use of ProblemDetail for HTTP error responses. (issue #…
182e68c 
…149 and PR #173) (#175)

* feat: Implements the use of ProblemDetail for HTTP error responses.

* fix: Fixing OpenAPI documentation and implementing date and time details in ProblemDetail.

* fix: Implements some adjustments to properties.

* fix: Adjusts the Time Sample property to the ISO 8601 standard.
@arey
Copy link
Member

arey commented Dec 28, 2024

Hi @thisdudkin could you please verify if the #175 did not already implement the RFC as you propose?

@thisdudkin
Copy link
Contributor Author

Hi @thisdudkin could you please verify if the #175 did not already implement the RFC as you propose?

Yes, this issue can be marked as solved ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@arey @thisdudkin