Fair point. The GraphQL integration was completed fairly early into the development of ArangoDB 3.1 and we had to prioritize other tasks over the maintenance of our sync wrapper to graphql-js.
I'll try to push out releases for 0.6 and 0.7 next week. Since 0.6 didn't introduce any breaking changes we should be able to update the bundled version to 0.6.2 with the next 3.1 bugfix releases but 0.7 (or 0.8 if it's out of beta) will have to wait until 3.2 due to the backwards incompatible changes.
Keep in mind that it will still be possible to use newer versions of graphql-sync directly, you just miss out on the Foxx/GraphQL integration as graphql-js relies on `instanceof` checks.
Also, the GraphQL integration literally fits in a single file and doesn't rely on any ArangoDB internals (just the Foxx router) so it will be possible to add your own copy of it to your code when the new version of graphql-sync is out.
Comments
Fair point. The GraphQL integration was completed fairly early into the development of ArangoDB 3.1 and we had to prioritize other tasks over the maintenance of our sync wrapper to graphql-js.
I'll try to push out releases for 0.6 and 0.7 next week. Since 0.6 didn't introduce any breaking changes we should be able to update the bundled version to 0.6.2 with the next 3.1 bugfix releases but 0.7 (or 0.8 if it's out of beta) will have to wait until 3.2 due to the backwards incompatible changes.
Keep in mind that it will still be possible to use newer versions of graphql-sync directly, you just miss out on the Foxx/GraphQL integration as graphql-js relies on `instanceof` checks.
Also, the GraphQL integration literally fits in a single file and doesn't rely on any ArangoDB internals (just the Foxx router) so it will be possible to add your own copy of it to your code when the new version of graphql-sync is out.