You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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:
Considerations:
The text was updated successfully, but these errors were encountered: