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

`print_schema` should be deterministic

Open
#135 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
graphql, python
Domain
api, backend

Research direction

Start by locating the print_schema entry point and any tests covering schema output. Check how object fields and field arguments are ordered, then verify that printing the same schema repeatedly produces identical output.

Written by the indexing model from the issue text.

Description

In our project, we commit a graphql schema to our repo. This is useful for running demos, tests and mocking data.

However, now we also want to be able to ensure that the schema is kept up-to-date with a CI check. Unfortunately, printing the schema twice, seems to not be guaranteed to print values in the same order (especially keys in object types, and field arguments). This makes consistency checks significantly harder.

It'd be great if there was a guarantee of determinism. Running the printer repeatedly, against a given schema always outputs the same file.

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.