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
I'm reaching out on behalf of the team at Hasura, where we've been utilizing the openapi-to-graphql library extensively. Specifically, we've integrated it within our services to facilitate users in creating actions from an OpenAPI specification.
Recently, we've noticed a surge in user requests, urging us to support OpenAPI Specification 3.1. Given the growing demand and the advancements in the 3.1 spec, it would be beneficial for the openapi-to-graphql library to consider this version.
Do you have a plan to implement support for version 3.1?
We can imagine two possible solutions:
Translate 3.1 to 3.0: this is similar to the current support for 2.1, using an external library or mechanism to downgrade the 3.1 specifications to 3.0.
Switch Primary Support from 3.0 to 3.1: and finding a method to translate from 3.0 to 3.1, as the library do now from 2.1 to 3.0
We understand each approach has pros and cons and would require a certain development effort.
We would like to know your thoughts and if there is any way that we could help.
Thanks!
Daniele
The text was updated successfully, but these errors were encountered:
@dancamma Currently, OtG is not being actively maintained. We are currently looking to onboard new maintainers. If that interests you at all, please let me know. Otherwise, sadly, development for OtG is paused for the time being.
Hello,
I'm reaching out on behalf of the team at Hasura, where we've been utilizing the openapi-to-graphql library extensively. Specifically, we've integrated it within our services to facilitate users in creating actions from an OpenAPI specification.
Recently, we've noticed a surge in user requests, urging us to support OpenAPI Specification 3.1. Given the growing demand and the advancements in the 3.1 spec, it would be beneficial for the openapi-to-graphql library to consider this version.
Do you have a plan to implement support for version 3.1?
We can imagine two possible solutions:
Translate 3.1 to 3.0: this is similar to the current support for 2.1, using an external library or mechanism to downgrade the 3.1 specifications to 3.0.
Switch Primary Support from 3.0 to 3.1: and finding a method to translate from 3.0 to 3.1, as the library do now from 2.1 to 3.0
We understand each approach has pros and cons and would require a certain development effort.
We would like to know your thoughts and if there is any way that we could help.
Thanks!
Daniele
The text was updated successfully, but these errors were encountered: