See Enabling your GraphQL Endpoint for further details. The path in AEM that responds to GraphQL queries, and provides access to the GraphQL schemas. Using your schemas, GraphQL presents the types and operations allowed for the GraphQL for AEM implementation.Schemas are generated by AEM based on the Content Fragment Models.
The GraphQL for AEM implementation is based on the standard GraphQL Java™ Library. GraphQL is used in production by hundreds of organizations of all sizes…”įor further information about the GraphQL API, see the following sections (among many other resources): It provides an alternative to REST-based architectures with the purpose of increasing developer productivity and minimizing amounts of data transferred. “…a data query language and specification developed internally by Facebook in 2012 before being publicly open-sourced in 2015. Put GraphQL over your existing backends so you can build products faster than ever before…”. “ …an open spec for a flexible API layer. It gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools.”. GraphQL provides a complete and understandable description of the data in your API. “ …a query language for APIs and a runtime for fulfilling those queries with your existing data. See the Release Notes for further details.
Graphql nested fragments install#
AEM Content Fragments work together with the AEM GraphQL API (a customized implementation, based on standard GraphQL), to deliver structured content for use in your applications.Ĭustomers using GraphQL should install the AEM Content Fragment with GraphQL Index Package 1.0.5. AEM Commerce consumes data from a Commerce platform via GraphQL. What about a non-breaking change, which still reverts part of it: you could output the data under attributes and the root object at the same time.GraphQL is used in two (separate) scenarios in Adobe Experience Manager (AEM): I understand there shouldn’t be a breaking change and I’m happy you follow the semver conventions. However, the GraphQL response in v4 feels very complicated and cumbersome. I think it should be clear that you had the best intentions with the change. Thank you very much for opening a space for a discussion. This meant unifying the REST and GraphQL data responses, error handling, filtering/paging system, ect. We have not entirely implemented the standard yet but our goal with the first release of Strapi v4 was to lay the groundwork so that we could continue to build on it without breaking changes. The primary goal behind this new structure was to pick some kind of standard for a response structure, ideally not reinvent the wheel and try to use an already existing standard. An above mentioned suggestion of including normalization libraries in best practices or even sponsored SDKs (like the Strapi-SDK-JS is) is one example of what we believe could benefit everyone. In the short term we would rather explore options to optimize using this response structure on the client side and see how we can assist. We do understand that it was not clear at the time during our RFC process this was the case and we are already doing retrospectives to improve this process. Recommend usage of something like normalizr for REST Users + potentially integrate a normalization library in the Strapi SDK JSĪt this time we are not prepared or planning to modify this data structure in the response, the time for that type of modification has passed as it should have been addressed during the RFC process. Remove Attributes and throw everything under data in GraphQL => Not possible due to breaking changes. Revert to v3 style in GraphQL => Not possible at this moment. JSON API structure of which this new system is based on:. Related comments the above mentioned issue (on GQL RFC PR): GRAPHQL API by Convly. Locked discussion topic issue: GraphQL Developer Experience improvements 🥇. Original v4 RFC for GraphQL: rfcs/xxxx-v4-graphql-api.md at v4/graphql-api. Original v4 RFC for REST: rfcs/xxxx-v4-rest-api.md at v4/rest-api. If you haven’t already please read the following documents, pull requests, or issues before commenting: 
This topic is not about population, please discuss that topic here: Discussion regarding default population of RESTĬurrent Status Post: Discussion regarding the complex response structure for REST & GraphQL (Developer Experience) - #35Īs mentioned in a news post in our Discord last week we wanted to setup this discussion around how the response structure is handled (nested data & populate) in Strapi v4.
0 kommentar(er)
