You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Discovery API resports nodes' names as their implemented Kind, ex. Realm or Pod. The GraphQL API just serializes the enum member's name directly, ie REALM and POD. In all of our current use cases this only amounts to a casing difference, but it would still be best if these were consistent between the two API endpoints.
The text was updated successfully, but these errors were encountered:
andrewazores
changed the title
GraphQL and Discovery API report node types as the enum members' names, not their Kinds
GraphQL and Discovery API disagree on nodes' names
Mar 11, 2022
It is possible to do it by wrapping the type in a GraphQL scalar and other such tricks, but this means that the GraphQL side of the implementation will have to duplicate all of the NodeTypes already declared by our internal Platforms API, which is what is exposed by the Discovery HTTP API.
The Discovery API resports nodes' names as their implemented
Kind
, ex.Realm
orPod
. The GraphQL API just serializes the enum member's name directly, ieREALM
andPOD
. In all of our current use cases this only amounts to a casing difference, but it would still be best if these were consistent between the two API endpoints.The text was updated successfully, but these errors were encountered: