docs: a value required only under a condition - checks: requiredWhen - #53
Open
delchev wants to merge 1 commit into
Open
docs: a value required only under a condition - checks: requiredWhen#53delchev wants to merge 1 commit into
delchev wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Documents the new row-level
checkskind (proposal IntentFile/intent-specification#70) on the entities spec page and the reference cheat sheet.required: truesays a value must always be there; most rules about a missing value are not like that - the value is needed for ONE way of handling the record and meaningless for the others. An invoice sent by e-mail needs the customer's e-mail address; one sent by post does not, and one handed over needs neither, sorequiredon the address is not the rule - and without a way to say the real one an e-mailed invoice reaches "sent" with nobody to send it to, silently.Covers the value (a field or a one-hop
Relation.field, cross-model included, and why an unset relation counts as absent), the closed and typed condition with both of its refusals, and the optionalstatus:gate whose presence decides when the rule is evaluated.🤖 Generated with Claude Code