Details
-
Story
-
Resolution: Obsolete
-
High
-
None
-
None
-
None
-
v2 Rolling sprint
Description
Projects and integrations that feature content editing / creation, but do not rely on symfony, need to be mapped to the fieldtype's business logic:
- list and type of input fields
- settings (ex: possible values in a select field)
- validation for those fields (min & max length, file size...)
For now, and it is what PlatformUI does, one would read the content type's field definitions using REST, and build the interface / validation based on what is exposed. While the API exposes constraints and settings, it doesn't expose the input expectations, meaning that each consumer must have its own form structure implementation foreach fieldtype.
The spike aims at picking a popular frontend tech, and identifying what eZ Platform must provide the consumer with to automate building a content edit/create UI. The idea is to reduce as much as possible the duplication of Platform's business logic on the consumer's side.
The spike should report on research for existing solutions: json-schema seems to cover this, but there might be others. Solutions that have a symfony counterpart should be considered as well.