graphql-python / graphql-python/graphql-core-legacy
Best way to capture errors
- Vorherrschende Sprache
- Python
- Sterne
- 372
- Forks
- 175
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
Do you have a good solution to hook in some sort of error reporting? I'm thinkin maybe some way to hook into `GraphQLLocatedError` when it is generated, but I dont know how to do that without forking the repo... python n00b
Also: for questions like this, is there a better place to ask this? I dont see a slack channel or any place to put this type of a question :(
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
The issue only identifies GraphQLLocatedError and does not name a repository file, test, or entry point. Start by locating where GraphQLLocatedError is generated and reviewing the existing error-handling flow. Done would require a clearly defined, supported way to connect error reporting without forking the repository.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- graphql, python
- Bereich
- api
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 15/100