-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add config.ui.isDisabled option #4866
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/mmc9i5is8 |
🦋 Changeset detectedLatest commit: bb162a9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 10 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should be isDisabled
as per #461, no?
Good point, it 💯 should. Will change 👍 |
Currently blocked on #4867 |
49746ee
to
8d8c638
Compare
8d8c638
to
7fbda04
Compare
7fbda04
to
225694c
Compare
225694c
to
f25a342
Compare
f25a342
to
b280da6
Compare
In particular, this is needed for our testing framework, where we want to spin up an express server for just the graphQL API.