Support config pages entity type

Created on 22 May 2024, about 1 month ago
Updated 10 June 2024, 16 days ago

Problem/Motivation

I would love to have config pages support.

Remaining tasks

I've already added the new graphql compose entity type. But the problem is if i want to request it i need a id. But since it is just 1 page per config page, we should be able to call it without a UUID. For now I use the edge query and just use parameter first with value 1, but this ofcourse is a dirty work around.

✨ Feature request
Status

Postponed: needs info

Version

2.2

Component

Code

Created by

πŸ‡§πŸ‡ͺBelgium CedricL

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • 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 Fixed

    Alternative option might be views?

  • Status changed to Active 28 days ago
  • πŸ‡¦πŸ‡ΊAustralia AlMunnings Melbourne
  • πŸ‡§πŸ‡ͺ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 16 days ago
  • πŸ‡¦πŸ‡ΊAustralia AlMunnings Melbourne
Production build 0.69.0 2024