Skip to content
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.

Sign up for GitHub

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

More precise definition of Mandatory #296

Merged
merged 4 commits into from
Nov 30, 2023
Merged

More precise definition of Mandatory #296

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3da13a4
More precise definition of `Mandatory`
HeikoTheissen Nov 21, 2023
ad5a6b7
Be less explicit about 0 and `false`
HeikoTheissen Nov 21, 2023
4792c1a
Mention draft activation
HeikoTheissen Nov 23, 2023
97bc19d
Merge remote-tracking branch 'origin/main' into FieldControl-Mandatory
HeikoTheissen Nov 30, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion vocabularies/Common.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -308,7 +308,7 @@
"@Core.LongDescription": "When changes are requested, the value of this annotation in the before-image or after-image\n of the request plays a role. These may differ if the value is given dynamically in the metadata.",
"Mandatory": 7,
"[email protected]": "Property is mandatory from a business perspective",
"[email protected]": "A request that sets the property to its initial value or null fails entirely if this annotation is `Mandatory` in the after-image of the request.\n\n This annotation value does not imply any restrictions on the value range of the property. For restricting the value range use e.g. the standard type facet `Nullable` with a value of `false` to exclude the `null` value, or terms from the [Validation vocabulary](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Validation.V1.md).",
"[email protected]": "A request that\n <br>- sets the property to null or an empty value or\n <br>- creates a non-[draft](#DraftRoot) entity and omits the property or\n <br>- activates a draft entity while the property is null or empty\n <br>fails entirely if this annotation is `Mandatory` in the after-image of the request.\n The empty string is an empty value. Service-specific rules may consider other values, also\n of non-string type, empty.\n Values in draft entities are never considered empty.\n Mandatory properties SHOULD be decorated in the UI with an asterisk.\n Null or empty values can also be disallowed by restricting the property value range with the standard type facet `Nullable` or terms from the [Validation vocabulary](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Validation.V1.md).",
"Optional": 3,
"[email protected]": "Property may have a value",
"[email protected]": "This value does not make sense as a static annotation value.",
Expand Down
Loading