-
Notifications
You must be signed in to change notification settings - Fork 90
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
Standardize Open Payment errors #1905
Labels
Comments
@sabineschaller Please assign this to me. |
Can you assign this issue to me so I can work on it? |
Hey @anurag629 & @Jacintomuambumba, did you end up starting on this issue? |
Iám working |
10 tasks
1 task
5 tasks
5 tasks
Reopening while I add additional related PRs |
5 tasks
This was
linked to
pull requests
May 8, 2024
5 tasks
5 tasks
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
We should standardize errors that get thrown in the Open Payments API, so we can return proper error codes and messages in the API response.
Potentially, we could do something like:
and then use a middleware to properly format those errors when thrown in the Open Payment routes.
This will also help standardize usage for the Open Payments client: https://github.com/interledger/open-payments/tree/main/packages/open-payments
The text was updated successfully, but these errors were encountered: