Skip to content

Turnback the GraphQL explorer update UI changes #2283

@EvelienIGNE

Description

@EvelienIGNE

We use Craft CMS with GraphQL integration to a React frontend.
We used to use the "Explore the GraphQL API" UI all the time but we HATE the update. It is super user unfriendly, especially when you're new with GraphQL and it takes a lot of time to figure it out.

I don't get why you would change it to this maze from the nice interface that it was before. We already were thinking of moving away from GraphQL but I'm afraid you will loose a lot of users because of this.

My advice (and from what I read online I'm most definitely not the only one wanting this; I don't see one positive comment about it anywhere) turn back the changes so that at least the "Explore the GraphQL API" is sort of easily usable.

This change has cost us a lot of money and time and as you can imagine we are not happy at all and our clients even less.

Thanks a lot in advance and for your hard work

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions