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

Add logging example to documentation

Open
#238 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Start by reading the issue referenced in #41 to understand the existing exception-handling change, then inspect the current documentation for the appropriate location. Add a documentation example showing logging and error handling for graphql-core's caught exceptions, and verify that it explains how to use the behavior in practice.

Written by the indexing model from the issue text.

Description

Judging by the issues on this package and graphene, a lot of users struggle with graphql-core's decision to catch all exceptions. I see that in #41 something was done to make this easier, but it's not clear how to use it. An example of logging/error handling in the documentation would go a long way.

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.