-
Task
-
Resolution: Fixed
-
Major
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
-
Nucleus 11, Nucleus 12
-
8
The framework expose publicly a lot of java implementation details, making it easy to misconfigure.
- implementation classes all over the place
- factory classes
- fields
- types
- converterClass
- multi fields
- entryResolution (can we have just the default one for now?)
- orderHandler (can we have just the default one for now or disable ordering by a boolean property?)
- itemProvider (can we have just the default one for now, the child provider?)
- propertyNameDecorator
- grid columns
- type
- valueProvider (no custom java in cloud anyway)
- renderer (HTML renderer could be replaced by an HTML column definition)
- descriptionGenerator
- causes
-
ANALYTICS-407 UI is broken on Magnolia 6.3
- Closed
- depends upon
-
MGNLPN-639 converterClass not configurable via YAML anymore
- Open
-
ADMINCTR-72 Hide implementation details from configuration
- Closed
-
CFGUI-144 Hide implementation details from configuration
- Closed
-
PAGES-603 converterClass not configurable via YAML anymore
- Closed
- is causing
-
MGNLUI-8802 ConfiguredFormDefinition#implementationClass is not public anymore
- Resolved
-
PAGES-591 Adjust config after changes by MGNLUI-7101
- Open
-
MGNLUI-7370 Replacement for text field type and converter
- Closed
- is depended upon by
-
ADMINCTR-72 Hide implementation details from configuration
- Closed
- is related to
-
MGNLDAM-1042 Minor problems are reported for dam-chooser in Definitions app
- Open
-
MAGNOLIA-8393 Definition app problems are based on read instead of write methods
- Closed
- relates to
-
MAGNOLIA-9356 DOC: Hide implementation details from configuration
- Closed