macroz / graphqlviz Goto Github PK

Hi,

It seems the introspection query returns a "data" element contaning the "__schema", where as the load-schema function expect the __schema to be the outer most key.

The workaround is to just strip the "data" dictionary by hand (or a simple script).

{ "data": { "__schema": { ... } } }

For the newbie,
For the neo fit not use to these technologies,
For the lazy, a ready to use package to run

Thank you

While GraphQL does not specify any standard for doing paging/collections, it seems that a convention is to have a XxxConnection-type and possilby a XxxEdge-type, which always contains a specific sets of fields and reference an instance of Xxx.

With larger graphs with many collections with paging, the Connect/Edge-types clutter the graph quite a bit. It would be nice to have a way of replacing any of these paging classes with a "one to many" connection in the dot-graph. This could be indicated with a star either at the arrow or prefixed/suffixed the connection name.

As there is no specification, this might be a bit tricky to get right, matching might have to be a bit flexible - and this might be a feature that is not on by default.

• Facebooks convension seems to be XxxConnection and XxxConnectionEdge.
• graphql-dotnet seems Edge-types has no incoming edges, only an outgoing connection to the underlying type. From the example dataset I can see the Connection-type also has a connection to the Edge-type (which sounds reasonable).

There does not seem to be any way to get credentials or use "standard" NTLM authentication when doint a live-server introspection query. An exception is thrown which contains the returned result, being a 401 status and a "WWW-Authenticate" ["Negotiate" "NTLM"]-header.

The simple workaround is be to manually do the introspection query and store the result to a file, and then feed the file into GraphQLviz.

Currently only the interface is rendered. Any objects implementing that interface are not.