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.
Comment | File | Size | Author |
---|---|---|---|
#2 | 3089087-2.patch | 62.39 KB | gordon |
Comments
Comment #2
gordon CreditAttribution: gordon at Heydon Consulting commentedHere is the patch which changes everything.
Comment #3
gordon CreditAttribution: gordon at Heydon Consulting commentedComment #4
blazey CreditAttribution: blazey at Amazee Labs commentedThanks Gordon, this is fantastic! I've tested it briefly and it looks great. I've noticed two things so far:
ConfigDeriverBase
might be redundant. We already have schema_cache_tags, schema_cache_contexts and schema_cache_max_age inGraphQLAnnotationBase
These two minor things won't hold me back from merging this patch right away :). The details can be discussed later.
Comment #6
blazey CreditAttribution: blazey at Amazee Labs commentedComment #7
blazey CreditAttribution: blazey at Amazee Labs commentedI've created 3 follow-ups