Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement a dynamic graphql schema #563

Open
wileymc opened this issue Sep 23, 2024 — with Linear · 0 comments
Open

Implement a dynamic graphql schema #563

wileymc opened this issue Sep 23, 2024 — with Linear · 0 comments
Assignees

Comments

Copy link
Contributor

wileymc commented Sep 23, 2024

Our schema uses #[guard] macros to enforce access for various users/roles/organizations which causes problems for the graphql playground.

{
  "error": "Invalid or incomplete schema, unknown type: EmbedOriginResult. Ensure that a full introspection query is used in order to build a client schema."
}

Introspection doesn't work in this context because of the field & resolver guards. The public facing API should not including these methods for introspection. I believe this can be achieved using async-graphql's dynamic schema feature though I am unsure of what the implementation should look like.

Our schema uses #[guard] macros to enforce access for various users/roles/organizations which causes problems for the graphql playground.

{
  "error": "Invalid or incomplete schema, unknown type: EmbedOriginResult. Ensure that a full introspection query is used in order to build a client schema."
}

Introspection doesn't work in this context because of the field & resolver guards. The public facing API should not including these methods for introspection. I believe this can be achieved using async-graphql's dynamic schema feature though I am unsure of what the implementation should look like.

@wileymc wileymc self-assigned this Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant