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

Exception handling API and Sentry #73

Closed
maddyjoe opened this issue Oct 25, 2022 · 0 comments · Fixed by #74
Closed

Exception handling API and Sentry #73

maddyjoe opened this issue Oct 25, 2022 · 0 comments · Fixed by #74

Comments

@maddyjoe
Copy link

maddyjoe commented Oct 25, 2022

As a young person I want to know when an exception error has happened and be told in a friendly-age appropriate way what has gone wrong

This is part 2 and dependent on part 1 Exception handling check and refactor#72 completing first.

What this ticket covers:

  • any changes to how the API handles and passes exception errors to front end application(s)
  • set up and config of Sentry
  • as an output to inform the UI (part 3) ticket can we provide a list of the errors so we can consider which might need some age-appropriate short copy creating

Considerations:

  • If possible expect we would want to be able to know in Sentry if the exception happened in WebComponent or the Standalone Editor?
patch0 added a commit that referenced this issue Oct 31, 2022
closes #73

Adds exception handling to the API to enable errors to be logged into
Sentry.

There was a general rubocop clean-up, and this has updated the tests
(mostly).

I've added a noddy test to the `create` operation, to ensure that Sentry
is called correctly. I've not added similar tests to the remix and
update services.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant