Show property values in the Properties Editor

Values retrieved from the Rest service must be shown in groups. These groups are very much like the choice fields and compound fields we already have in the content editor.

For the component properties editor we need these types:

• String
• Boolean
• Date (keep the calendar widget and 'set to today' functionality)
• Number
• DocumentLink
• Dropdown -> this field was used in create content step 1 for the document types. It is not used in the content editor.

The numeric values supported by the @Parameter tag are: short, int, long, java.lang.Short, java.lang.Integer, java.lang.Long. It is expected that the Number field that we have in the Angular app suffices supporting this. All values are of course stored as strings, negative numbers are allowed, if the value of a field exceeds the capacity of the type, the getter in Java just returns 0.

Make sure to implement the validation for required component properties.

Make sure to hide properties that are marked as 'hideInChannelManager' = true.

Component properties can be divided into groups with a group label. This introduces an extra hierarchy level in the presentation logic. When there is no name for a fieldgroup a default group title "Property group" is shown. The groups are shown collapsible like we have for compounds.

Outstanding question to cdekort: will there be any client-side state involved here, i.e. remember which groups were collapsed, or do we always open the form with all groups opened? Answer: no, not at the moment. Always show them collapsed when opening the editor.

About the styling of the groups: in the content editor they have a line at the left hand side of the group, that turns blue when the focus is on the group. We will not apply this styling to the groups in the component editor.

There are subtasks for every field type. The code for each type has to move up in hierarchy in the code tree, now that it is going to be used by the content editor as well was the component properties editor.