Drupal graphql revisions code#

Drupal graphql revisions code#

In this case I don't think a higher version number necessarily means it's better, just that it's or perhaps an explanation of the differences (and future support plan) of the two versions can be added to the project page to help people understand the differences?Īs for examples for the 4.x version, we're actively developing with the 4.x version in Open Social, which is open source: goalgorilla/open_social#1994 I'd encourage you to dive into the code to see what we're doing. I think if the automated exposure is what you're looking for then it makes more sense to just use the 3.x version of the module. This could be a separate module in contrib or a submodule of the GraphQL module. Lets look beyond simply dumping Drupal's internal data representation out into the rest of the world and instead see if we can build a schema builder that allows a user through a UI to describe the structure of their graph based on what data is available. One thing that all these things have in common though is that Drupal has a great internal system of describing how these things differ (bundles) and are connected (entity relations).

Exposing all those as the same 'Group' data structure, isn't great practice from an API perspective. In Open Social the group module is used in 3 different contexts (groups, discussions and courses). What does it mean to expose a Paragraph Entity? The group module also provides a very flexible building block that may be used in different manners. Examples are that all nodes would appear to be related even if they have very different functions. However, whatever was best for Drupal may not be most useful to (or even desired for) your front-end consumers.

I think not automatically exposing anything in version 4 of this module is actually a feature rather than a detriment.Īny automated mapper (be it for REST, JSON API or GraphQL) will use the data structure that Drupal uses.