Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Best way to capture errors

Open
#93 1 comment 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
graphql, python
Domain
api

Research direction

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.

Written by the indexing model from the issue text.

Description

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 :(

Dominant language
Python
Stars
371
Forks
175
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from graphql-python/graphql-core-legacy

All issues in graphql-python/graphql-core-legacy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.