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
{{ message }}
This repository has been archived by the owner on Jun 18, 2024. It is now read-only.
Looks promising as an action API, happen to know whether it could perform data transformation on the fly or at rest using a key:value mapping to an in-memory schema against another schema xml/json/yaml as a client-side Javascript transform it would be interesting. Thanks for the question
That SWAPI example is getting so much play right now 😆
"whether is could perform data transformation on the fly": It's not exactly a logic layer, but could very well be an API into one or compose many (e.g., microservice stuff). In fact there are existing bindings for many different databases/ORMs. It can do everything REST can do, but has some relevant advantages for data interoperability challenges such as those faced when using open data.
What are your thoughts on leveraging GraphQL for making better open APIs?
http://graphql.org/
We're starting research down this path and would be happy to hear from potential contributors:
https://github.com/OpenGraphQL/opengraphql-organization/issues/1
The text was updated successfully, but these errors were encountered: