Non-null Int types for "first" argument are not accepted by rule "relay-connection-arguments-spec"

Description

  notablePeople(first: Int!, after: ID): NotablePersonConnection!

  users(first: Int!, after: ID, where: UsersQueryWhereInput): UserConnection!
    @requireOneOfRoles(roles: [MODERATOR])

  notablePeopleEvents(
    first: Int!
    after: ID
    where: NotablePersonEventsQueryWhereInput
  ): NotablePersonEventConnection!

Contributor guide

Tech stack

javascriptgraphql

Domain

apitooling

Issue type

bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

under 1 hour

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

mostly clear

Prerequisites

basic GraphQL knowledgefamiliarity with graphql schema linter

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

55

Research direction

The issue is in the `relay connection arguments spec` rule which likely validates that connection fields have `first`/`last` arguments of type `Int`. The current implementation does not accept non null `Int!` types. Investigate the rule's source code in the repository (likely in `src/rules/relay connection arguments spec.js`) to understand how type checking is performed. The fix may involve allowing both `Int` and `Int!` by updating the type comparison logic. Check the GraphQL spec for Relay connections to confirm that non null `Int` is valid according to the spec.