Repository navigation
feat(content): files collections with their own fields per file - #58
Merged
Merged
Conversation
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
fields.createis forced to false), deleting is refused except dropping a draft.{slug}or?slug=(AI assistant, autosave), so validation and rendering use the file's own fields.i18non a files collection is refused,seoand relations may use fields of any file.sumigo.ymlform gets a Folder / Fixed files switch and a file list, and the YAML completion knows the new keys.sumigo.ymlreference, README and introduction, Decap differences table updated.Tests
TestFilesCollectionsResolveTheirFiles: paths, per-file fields, invalid names and paths refused.TestFilesCollectionsEditFixedFiles: list with labels, empty missing file, per-file required fields, no create nor delete, unknown file 404.