Cannot generate grapqhl schema for Stripe API

Describe the bug Not able to generate Graphql Schema with openapi-to-graphql cli using Stripe’s API OAS definition

To Reproduce Steps to reproduce the behavior:

1. install the openapi-to-graphql-cli
2. try generating schema by running: openapi-to-graphql https://api.apis.guru/v2/specs/stripe.com/2019-03-14/swagger.json

Expected behavior The graphql server starts with generated Stripe API schema

Actual result Getting the following error:

openapi-to-graphql https://api.apis.guru/v2/specs/stripe.com/2019-03-14/swagger.json(node:54348) ExperimentalWarning: The http2 module is an experimental API.
OpenAPI-to-GraphQL creation event error:  Cannot read property 'schema' of null

Additional context Up to date latest OAS Stripe’s spec can be grabbed here: https://github.com/stripe/openapi/blob/master/openapi/spec3.json *same generation result as described above

[Alan-Cha]

Hey everyone! I know this has been a very, very long awaited feature but it is finally out. We have support for allOf, anyOf, oneOf, and not as well as more robust fallback mechanisms and we can officially say that we can wrap the Stripe API in GraphQL with the release of OtG v2.0.0!

In the screenshot, you can see that we are able to successfully run a query against the Stripe API.

Let me know what your experience is! Thanks for sticking around!

[Alan-Cha]

I found the problem. OAS uses a few keywords to combine schemas, namely “oneOf”, “anyOf”, “allOf”, and “not”. Currently OtG only supports “allOf”. Stripe makes use of (at least) “anyOf”.

These keywords throw a wrench in the GraphQL ecosystem. Because GraphQL enforces a strong typing system and combining schemas muddles the typing. Implementing “allOf” is easy to do, but “oneOf” and “anyOf” are tricky, and “not” may be impossible (we will probably resort to stringifying the data or use the GraphQL JSON type). For more information, see #14.

For the time being, I have improved reporting with #199.