Separate GraphQL schema for website #6504
Locked
mbrowne
started this conversation in
Feature requests
Replies: 1 comment
-
|
Answered in the Q&A session - see #6597 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, it looks like currently there is always just one GraphQL schema in Keystone, which is used both for the Keystone admin system and for your app.
Are there any plans to allow for the creation of a separate GraphQL endpoint to be used for your website or app that can be extended/customized without affecting the GraphQL API used by the admin system? This is important when implementing a view-model pattern.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions