Repository navigation
Record the storage nullability rules and index shapes in the specification - #2732
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.
Closes #2731
Moves the contracts that lived only in the PR #2729 body into section 4.3: the nullability rules, the default lengths, the
[Indexed]index shapes for base and_i18ntables and the index naming.integeris nowbigint, andcms_referenceandcms_versionlist theiridv7 key. Section 4.4 names the draft placeholder rule, and Appendix A gainsix_cms_article_published_on. Each rule was checked againstContentModelBuilder,FieldStorageandSystemModelBuilder; where the PR body and the code differed, the spec follows the code. Docs only.Dependencies: none.
Acceptance
[Indexed]index shapes for base and_i18ntablesix_cms_article_published_on