Update GraphQL to latest version and add / improve support for passed arguments #2367
Comments
johannilsson
added a commit
to johannilsson/OpenTripPlanner
that referenced
this issue
Nov 14, 2016
* Update GraphQL library to latest stable version (2.2.0) * Add support for parsing arguments if they're sent as a string * Add support for operationName to the graphql endpoint * Fix issue with findClosestStopsByWalking where the routing context must be set after batch Fix opentripplanner#2367
johannilsson
added a commit
to johannilsson/OpenTripPlanner
that referenced
this issue
Nov 22, 2016
|
Does anyone of you guys @johannilsson or @hannesj know anything about GraphiQL (https://github.com/graphql/graphiql). One of our developers looked at it, and it could make it easier to develop against GraphQL. |
|
@barslett you might even like a native wrapper around it https://github.com/skevy/graphiql-app. More great GraphQL resources here https://github.com/chentsulin/awesome-graphql |
|
@barslett We are using it at http://dev.hsl.fi/graphql/console/ Also the locally installable version for development. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Arguments sent to the GraphQL endpoint is sent as a string from GraphiQL and needs to be deserialized before they're passed to the GraphQL library. Other GraphQL implementations also seems to handle this case.
The GraphQL version OTP is currently on does not work with complex types sent as arguments, this has been fixed in newer versions of the library.
The text was updated successfully, but these errors were encountered: