Added docu for @Common.FieldControl validation #1474
Conversation
This file contains 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
Co-authored-by: René Jeglinsky <rene.jeglinsky@sap.com>
|
@renejeglinsky Do you have an idea why the job is failing ? The broken links are not related with my changes. |
| @@ -926,6 +926,12 @@ entity Foo { | |||
| ``` | |||
|
|
|||
|
|
|||
| ### `@Common.FieldControl` {#common-fieldControl} | |||
There was a problem hiding this comment.
I'd rather add that after @mandatory/readonly section as this belongs together.
In addition, we could add that as a warning that numeric and dynamic values are not evaluated by the runtime.
There was a problem hiding this comment.
@johannes-vogel I thought it is good to be added right before 'Custom logic' ,as if they are numeric the customer has to use the custom logic.
This is fixed. |
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.
Related to https://github.tools.sap/cap/issues/issues/17261