Gentics Mesh Version, operating system, or hardware.
v0.24.0
If you want to use GraphQL, you always have to specify in which project you want to query data. This does not make sense if you want to get data that is not project specific. The following entities are not project specific:
Users
Groups
Roles
Schemas
Microschemas
Because of this, you can't actually use GraphQL to query any of the above types if there is no project. This should be made possible.
Solution
Create a new endpoint /api/v1/graphql (and also /api/v1/graphql/browser) which has the same fields as the project specific ones, except those that are project specific. We also have to be careful to remove all nested fields that reach project specific data (e.g. schemas -> nodes)
In the long term it would be better to remove project specific APIs and design the GraphQL API in a way that allows to fetch project specific data from the global endpoint.
Gentics Mesh Version, operating system, or hardware.
If you want to use GraphQL, you always have to specify in which project you want to query data. This does not make sense if you want to get data that is not project specific. The following entities are not project specific:
Because of this, you can't actually use GraphQL to query any of the above types if there is no project. This should be made possible.
Solution
Create a new endpoint
/api/v1/graphql
(and also/api/v1/graphql/browser
) which has the same fields as the project specific ones, except those that are project specific. We also have to be careful to remove all nested fields that reach project specific data (e.g. schemas -> nodes)In the long term it would be better to remove project specific APIs and design the GraphQL API in a way that allows to fetch project specific data from the global endpoint.