69badf2a66
We should capture graphQL exceptions thrown in the FE in Sentry. All the more so as we have just cleaned back-end errors in sentry, preventing 4xx errors from being wrongfully sent to sentry. Those 4xx errors should, except for `Unauthenticated` and `Forbidden` errors (for now - this list can evolve), trigger a sentry FE error, as we are not suppose to let users of the product interface trigger queries that will fail with 4xx errors (for instance a malformed input). We still miss an efficient way to group those errors together in sentry. It could be the message but the message may be different for each user if it contains user-specific data, and we don't always have control on the message. This can be done later as we iterate on improving sentry
Run yarn dev while server running on port 3000