This mechanism does not apply to property of array/items elements in the schema. These properties will be textfield (text) regardless of property spec.
Expected Behavior
Same validation behavior as with single value properties by changing the form element type.
Steps To Reproduce
Create a dataset
add a "Related document"
enter an invalid URL for the "Related Document" like "test"
Save dataset
You will notice a validation error message "The attribute should match 'uri' format." All fields in the form are marked red, so you do not know which field is affected.
This contrasts to entering a invalid URL in the "Data Dictionary" field. Here the validation error will mark the affected field with corresponding message (HTML5 validation I suppose).
Current Behavior
Some property specs in the schema bring up special form element types in the JSON form widget.
For example: specifying property spec "format" with a value of "uri", changes the input type to "url" instead of default type textfield (text).
This is done in the StringHelper class.
This mechanism does not apply to property of array/items elements in the schema. These properties will be textfield (text) regardless of property spec.
Expected Behavior
Same validation behavior as with single value properties by changing the form element type.
Steps To Reproduce
Relevant log output (optional)
No response
Anything else?
No response