getsentry / getsentry/sentry-javascript
node-integration-tests: port GraphQL suites to span streaming
- Lingua principale
- TypeScript
- Stelle
- 8.7k
- Fork
- 1.8k
- Merge medio
- 1g 17h
- PR unite (30g)
- 523
Descrizione
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.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- graphql, node.js, typescript
- Ambito
- testing-qa
- Tipo di issue
- Refactoring
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Attiva
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 68/100