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

add support for strict_type connections

Open
#429 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
graphql, python, sqlalchemy
Domain
api, backend, databases

Research direction

Start by tracing how the node Meta.strict_type setting reaches connections and how SQLAlchemyConnectionField constructs sorting when the node type is NonNull. Reproduce the nullable edge-list behavior and constructor failure described in the issue. Done means node metadata can set strict_type on the connection and the field constructor handles the NonNull node correctly.

Written by the indexing model from the issue text.

Description

Currently the strict_type=True option on the Meta class for a node is ignored and the connections end up having nullable values in the edge list. If you override the connection_class to set the strict_type on the connection, the SQLAlchemyConnectionField constructor fails because it does not unwrap the NonNull from the node before trying to set up the sort.

Ideally it should be possible to set the strict_type option on the connection via metadata on the node class.

Dominant language
Python
Stars
985
Forks
224
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

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/graphene-sqlalchemy

All issues in graphql-python/graphene-sqlalchemy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.