-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 field groups #8088
Add field groups #8088
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
🦋 Changeset detectedLatest commit: 1157235 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 1157235:
|
bd4c135
to
93a14ae
Compare
93a14ae
to
26c75b6
Compare
5379c58
to
ffa46b9
Compare
ffa46b9
to
aa936ed
Compare
aa936ed
to
965c3f7
Compare
965c3f7
to
4bf5ccd
Compare
633796c
to
179e152
Compare
initialSort: graphql.field({ type: KeystoneAdminUISort }), | ||
...contextFunctionField('isHidden', graphql.Boolean), | ||
isSingleton: graphql.field({ type: graphql.Boolean }), | ||
isSingleton: graphql.field({ type: graphql.nonNull(graphql.Boolean) }), |
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.
This is an unrelated thing I noticed when re-generating the types for the admin meta query, I don't think it was intentionally nullable. Types elsewhere assumed it was non-nullable so I've made it non-nullable.
179e152
to
8c085bd
Compare
8c085bd
to
708861d
Compare
This adds the ability to group fields together in the Admin UI with a label and description