You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/readme-generic-ui.md
+18-2Lines changed: 18 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,6 +52,14 @@ Each field definition supports the following properties:
52
52
53
53
- `"label"`: Display name for the field
54
54
- `"property"`: JSON path to the resource property (string or array of strings for fallback values)
55
+
- `"propertyField"`: In case the property is a scalar value that represents an object, this property can be used to specify the field to be used for display within that object
56
+
- `"key"`: The name of the field to be used for display
57
+
- `"transform"`: An array of text manipulations to be applied to the value, the available are:
58
+
| 'uppercase'
59
+
| 'lowercase'
60
+
| 'capitalize'
61
+
| 'decode'
62
+
| 'encode'
55
63
- `"jsonPathExpression"`: Alternative JSONPath expression for complex data access (takes precedence over `property`)
56
64
- `"required"`: Boolean flag indicating if the field is mandatory (for create views)
57
65
- `"values"`: Array of predefined values for selection
@@ -106,7 +114,7 @@ Below is an example content-configuration for an accounts node using the generic
0 commit comments