Background
We want to provide better GraphQL support with Sentry SDKs, frontend to backend. Work has already begun on some mobile platforms. There is also already some implementations for GraphQL server and client side. With the current work we want to ensure that the strategy to ensure proper connected errors and grouping works from backend to frontend. Java already has an integration for GraphQL.
Proposal
Java SDK should set context for GraphQL on errors same as what is done for Mobile SDK to ensure the value add from Frontend to Backend
Definition of Done TBC:
Further context:
getsentry/sentry#50230
Background
We want to provide better GraphQL support with Sentry SDKs, frontend to backend. Work has already begun on some mobile platforms. There is also already some implementations for GraphQL server and client side. With the current work we want to ensure that the strategy to ensure proper connected errors and grouping works from backend to frontend. Java already has an integration for GraphQL.
Proposal
Java SDK should set context for GraphQL on errors same as what is done for Mobile SDK to ensure the value add from Frontend to Backend
Definition of Done TBC:
Further context:
getsentry/sentry#50230
feat(graphql): Add special rendering logic for graphql requests sentry#50764
Ideally sentry-graphql, we could do code sharing with sentry-apollo, both written in Java