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

Handle application errors #110

Closed
Tracked by #608
thekaveman opened this issue Aug 3, 2022 · 1 comment · Fixed by #129
Closed
Tracked by #608

Handle application errors #110

thekaveman opened this issue Aug 3, 2022 · 1 comment · Fixed by #129
Assignees

Comments

@thekaveman
Copy link
Member

thekaveman commented Aug 3, 2022

See Flask - Handling Application Errors

Specifically, we should look at Returning API Errors as JSON.

  • 403 (forbidden, not authenticated/authorized)
  • 404 (endpoint not found)
  • 500 (other application error / Exception)
@thekaveman thekaveman moved this to Backlog in Digital Services Aug 3, 2022
@thekaveman thekaveman added this to the Courtesy Cards milestone Aug 3, 2022
@machikoyasuda
Copy link
Member

@thekaveman thekaveman moved this from Backlog to This Sprint (Month) in Digital Services Aug 4, 2022
@machikoyasuda machikoyasuda self-assigned this Aug 8, 2022
@machikoyasuda machikoyasuda moved this from This Sprint (Month) to In Progress in Digital Services Aug 16, 2022
Repository owner moved this from In Progress to Done in Digital Services Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants