getsentry / getsentry/sentry-javascript
node-integration-tests: port GraphQL suites to span streaming
- Langage dominant
- TypeScript
- Étoiles
- 8.7k
- Forks
- 1.8k
- Merge moyen
- 1 j 17 h
- PR mergées (30 j)
- 523
Description
Follow the porting recipe in the parent issue.
Small group, but the span names change the most: GraphQL phase spans now use the low cardinality fallback name and carry `graphql.processing.type`, and the segment name update from `useOperationNameForRootSpan` lands on the segment span instead of the transaction name.
## Suites
* `tracing/apollo-graphql`, `tracing/apollo-graphql/resolvers`, `tracing/apollo-graphql/useOperationNameForRootSpan`
* `tracing/graphql-tracing-channel`, `tracing/graphql-tracing-channel/resolvers`, `tracing/graphql-tracing-channel/useOperationNameForRootSpan`
* `aws-serverless/graphql/useOperationNameForRootSpan`
No `-streamed` twins exist for this group.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Start with the parent issue's porting recipe, then inspect the listed suites under tracing/apollo-graphql, tracing/graphql-tracing-channel, and aws-serverless/graphql. Update the suites for the specified GraphQL span names, processing type, and segment-name behavior; done means all listed suites are ported and their tests pass.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- graphql, node.js, typescript
- Domaine
- testing-qa
- Type d'issue
- Refactorisation
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- Active
- Clarté
- Plutôt claire
- Accessibilité débutants
- 68/100