Releases: IBM/openapi-to-graphql
Releases · IBM/openapi-to-graphql
OpenAPI-to-GraphQL v1.6.1
- Do not throw errors when dealing with
anyOf
,oneOf
, andnot
in JSON schema- We still do not handle these features. They are a work in progress.
- Do not add extraneous descriptions to the GraphQL interface
- Code improvements
Special thanks to @wtrocki for contributing to this release!
OpenAPI-to-GraphQL v1.6.0
- Improved support for
allOf
in JSON schemas
Special thanks to @prevuelta for contributing to this update!
OpenAPI-to-GraphQL v1.5.0
OpenAPI-to-GraphQL v1.4.1
- Fixed bug where input object types were not properly created for object schemas that did not have properties.
OpenAPI-to-GraphQL v1.4.0
- Support for GraphQL ID scalars
- If a string is of format
UUID
, it will be mapped to a GraphQL ID
- If a string is of format
- Added the
idFormats
option- Allows for greater flexibility over GraphQL ID scalars
Special thanks to @omarchehab98 for contributing to this update!
OpenAPI-to-GraphQL v1.3.0
- Objects with no properties fields are stored in an arbitrary JSON type
- GraphQL object types are very strict but OAS does not enforce that object schemas must have properties fields. We support these objects by using GraphQL JSON type.
- General code improvements
OpenAPI-to-GraphQL v1.2.0
- Fixed bug with CLI not being able handle a remote YAML file
- Added equivalentToMessages option
- Made fillEmptyResponses option less restrictive
- Improved error handing
- Enhanced documentation by sorting options
OpenAPI-to-GraphQL v1.1.0
- Support content property in parameter objects
- Stringify objects with no
properties
fields- GraphQL object types are very strict but OAS does not enforce that object schemas must have properties fields. For better compatibility, we recursively stringify objects with no
properties
, which should greatly increase compatibility with in-the-wild OASs.
- GraphQL object types are very strict but OAS does not enforce that object schemas must have properties fields. For better compatibility, we recursively stringify objects with no
OpenAPI-to-GraphQL v1.0.1
- Fix bug with creating field names for objects
Special thanks to @JennieJi for contributing to this update!
OpenAPI-to-GraphQL v1.0.0
Renamed OASGraph to OpenAPI-to-GraphQL
- Multi-OAS support
- Create GraphQL interfaces using multiple APIs
- Inter-OAS links
- Allows you to create nested objects the resolve on different APIs
- Custom resolvers
- Allows complete control over the generated resolvers. Opens many new doors such as creating resolvers that do not depend on a REST API backend or implementing caching.
- Add addLimitArgument option
- Allows to constrain the size of returned lists
- Added cookie authentication
- We now have full API key location support (i.e. "query", "header", and "cookie")!
- Exposed Request options, allowing fine control over generated resolvers
- Error extensions
- Errors during query execution are now clearly displayed
- Collapse links so that GraphQL object types can use links defined in different OAS operations objects
- Use Prettier for consistent formatting
- Simplified code base
- Improved warning handling
Regarding CLI-specific improvements:
- CORS support
Special thanks to @thejibz, @JamesDuf, @jduffy3, @SrChip15 for contributing to this update!