Skip to content

Lost astNode in schema created by introspection query #394

Closed
@Code-Hex

Description

@Code-Hex
Owner

The generation logic relied on the schema passed from graphql-codegen. If this was a schema generated based on introspection, the astNode information was lost, so it seems that it was not possible to determine whether each schema was an enum or a scalar.

This issue was reported here:

graphql/graphql-js#1575

Originally posted by @Code-Hex in #386 (comment)

Activity

added a commit that references this issue on Jun 10, 2023
e80fd49
added a commit that references this issue on Jun 10, 2023

Merge pull request #395 from Code-Hex/fix/394

25370e3
Code-Hex

Code-Hex commented on Jun 10, 2023

@Code-Hex
OwnerAuthor
maoosi

maoosi commented on Jun 10, 2023

@maoosi

@Code-Hex working great, thanks again for fixing it so fast!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @maoosi@Code-Hex

      Issue actions

        Lost astNode in schema created by introspection query · Issue #394 · Code-Hex/graphql-codegen-typescript-validation-schema