Hi,

It seems that we were working on the GraphQL module at the same time. I have built a much more comprehensive version which uses the config schema to build object which can be accessed much easier. Such as if we are using the `text_format` config it will not only give you access to the text and the formatter, it will also give you a virtual field which will give you the processed text, the same as if you were reading the `body` field from an entity.

Also since there is so much very sensitive data held in the config I have made it so that the config items exported to graphql are very restricted and only have items which are set in the settings.php.

CommentFileSizeAuthor
#2 3089087-2.patch62.39 KBgordon
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

gordon created an issue. See original summary.

gordon’s picture

FileSize
62.39 KB

Here is the patch which changes everything.

gordon’s picture

Status: Active » Needs review
blazey’s picture

Status: Needs review » Reviewed & tested by the community

Thanks Gordon, this is fantastic! I've tested it briefly and it looks great. I've noticed two things so far:

  1. The caching in ConfigDeriverBase might be redundant. We already have schema_cache_tags, schema_cache_contexts and schema_cache_max_age in GraphQLAnnotationBase
  2. the field names start with a lower-case letter, so configSystemSite would look more consistent

These two minor things won't hold me back from merging this patch right away :). The details can be discussed later.

  • blazey committed 190fd07 on 8.x-1.x authored by gordon
    Issue #3089087 by gordon, blazey: Module rewrite to give more structured...
blazey’s picture

Status: Reviewed & tested by the community » Fixed
blazey’s picture

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.