Repository navigation
Update from code changes: document collection field defaults - #398
Merged
Merged
Conversation
yash-pouranik
temporarily deployed
to
mintlify/18e5b791 - urBackend-frankfrut PR #398
August 21, 2026 05:09 — with
Render
Destroyed
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
yash-pouranik
approved these changes
Aug 23, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the new field-level default values and the requirement that collections must contain at least one field.
Changes
concepts/collections-schemas.mdx, covering supported types (String,Number,Boolean), the non-required rule, type matching, and the auto-clear behavior when a field is marked required.400response returned when creating or editing a collection with an empty schema.Context
Follows #394, which adds default-value support to the manual builder and AI Collection Creator and enforces a minimum of one field on create/edit endpoints.