Meta da of the content node is simple yaml represented as map<string, object> in the backend. This means, at the moment we only support these simple fields. It is possible to make some kind of custom field type by using a combination of fields, but this workaround is a bit dirty.
What if we support fields in meta data.every field would have a name, type and a map as values.
We need'
For templates:
meta.getfield
field.name
field.type
field.get(value1)
It must be possible to update fields via rpc in the manager.
Examples:
Geo location
Address
Meta da of the content node is simple yaml represented as map<string, object> in the backend. This means, at the moment we only support these simple fields. It is possible to make some kind of custom field type by using a combination of fields, but this workaround is a bit dirty.
What if we support fields in meta data.every field would have a name, type and a map as values.
We need'
For templates:
meta.getfield
field.name
field.type
field.get(value1)
It must be possible to update fields via rpc in the manager.
Examples:
Geo location
Address