Added docu for @Common.FieldControl validation

[mariayord]

Related to https://github.tools.sap/cap/issues/issues/17261

[mariayord]

@renejeglinsky Do you have an idea why the job is failing ? The broken links are not related with my changes.

[johannes-vogel]

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.

[mariayord]

@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.

[chgeo]

Do you have an idea why the job is failing ? The broken links are not related with my changes.

This is fixed.

[chgeo]

Will address the broken links @mariayord

[mariayord]

@chgeo I don't understand what is going on with the links. I see now Daniel added a space between assert and .unique @assert .unique. I will change this also for FieldControl ... I have to correct also the link for FieldControl

[chgeo]

@mariayord this is tricky because we use special characters like @ in the heading for which VitePress computes different anchors like common-fieldcontrol than the MD editor in VS Code (commonfieldcontrol) . See the difference? ;)

So either

• Use plain names in titles
• Or add additional anchors like here.

[mariayord]

@chgeo OK, in this case I have to add again the anchor... Thanks!
The space between names in annotations is strange for me, is there any reason ?