- Issue created by @cedricl
- π¦πΊAustralia almunnings Melbourne, π¦πΊ
I'm not suuuuper across this module
But from memory, the config pages settings can be exposed as tokens?You could then use those tokens in the provided "custom info" settings to expose the settings. If that helps?
Quick search, similar thread:
https://www.drupal.org/project/graphql_compose/issues/3361379#comment-15... β¨ Expose Configuration Type Entities for Site-Wide Data FixedAlternative option might be views?
- Status changed to Active
6 months ago 10:45pm 28 May 2024 - π§πͺBelgium cedricl
hi almunnings,
I'm not really a fan of the tokens method since, i like my data spread in seperate query instead of everything in the pageInfo, but this indeed covers most use cases for users. I'll stick to using the edges method i found for now. If i find the time I will update the module so we don't have to use a UUID for a single query. Can be put on hold for now
- π¦πΊAustralia almunnings Melbourne, π¦πΊ
Yeah I struggled with the structure of some of these config entities. I understand itβs a fieldable entity, but you then are creating an entire bundle type for one config set?
Its probably worth your while stepping outside of graphql compose to get your bespoke structure, you could introduce a new query that returns just one config entity without any args pretty easily, and you could return the config entity and let gqlc handle all the fields for you
Maybe it just isnβt fitting the entity queries provided by gqlc per se.
I can help you make a little module if youβd like?
- Status changed to Postponed: needs info
6 months ago 9:41am 10 June 2024 - Status changed to Closed: outdated
5 months ago 12:20pm 8 July 2024