question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

GraphQL Voyager not compliant with latest specs, breaks HotChocolate

See original GitHub issue
voyager.min.js:82 Uncaught (in promise) Error: Name "__AppliedDirective" must not begin with "__", which is reserved by GraphQL introspection.

Name "__DirectiveArgument" must not begin with "__", which is reserved by GraphQL introspection.
    at voyager.min.js:82:186809
    at voyager.min.js:82:186870
    at Vn (voyager.min.js:82:187038)
    at n.schema (voyager.min.js:82:194555)
    at sr (voyager.min.js:82:194678)
    at gr (voyager.min.js:82:196715)
    at t.updateIntrospection (voyager.min.js:82:248696)
    at voyager.min.js:82:248557

This was first brought to the attention of the HotChocolate team in https://github.com/ChilliCream/hotchocolate/issues/5154, but it seems that the __DirectiveArgument is indeed part of the official spec as an official type, but as a DRAFT feature. Could we please have this fixed? Thanks.

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
LunaticMuchcommented, Jun 16, 2022

@SpiritBob correct and because it’s draft, it’s not usable. graphql-js library does not support it. I doubt you can find another supporting it.

You should refrain from using it. If you decide to use it, you need to accept the risk.

0reactions
kikaragyozovcommented, Jun 16, 2022

@SpiritBob this is a issue of GraphQL Voyager as they do apparently not support these types. The __DirectiveArgument is a offical introspection type, but it’s a DRAFT feature on the spec. I woudl suggest to raise this issue on the graphql voyager repository, as HC is spec compliant in this case

Could you please toss a link to where they specify that it’s an official introspection type? Latest working draft doesn’t specify it, unless my CTR +F is playing tricks on me. https://spec.graphql.org/draft/

@SpiritBob Its this feature graphql/graphql-spec#300. It’s a stage 0 spec draft so hasnt made it into the offical draft specification. The introspection types are returned by the normal introspection aswell, but are not part of the SDL.

Read more comments on GitHub >

github_iconTop Results From Across the Web

GraphQL voyager breaks with large schemas · Issue #129
When I try to use GraphQL voyager with a schema that is about 4500 lines long it breaks, (it just displays a blank...
Read more >
ASP.NET GraphQL server with Hot Chocolate
Non -breaking changes can continue as they would with REST, adding properties to entities (as you would with response models in REST), continues ......
Read more >
GraphQL - Hot Chocolate 0.8.0
GraphQL Voyager is a nice schema explorer that can be useful ... a cool new chillicream compliant name like Hot Chocolate or Green...
Read more >
HotChocolate.AspNetCore.Voyager 10.5.5
Contains a GraphQL Voyager for ASP .Net core that can be used with the Hot Chocolate GraphQL server.
Read more >
Tfu - River Thames Conditions
Felt tape joanns, Wgs reaper 30 review, Glutax 600gs ultrafiltration, Karwia pokoje 3 ... Pc engine cd rom not spinning, Essentials group manager...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found