Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Modify the target property name , by appending a locale suffix or by prepending a composite field prefix. This is now done by concrete PropertySet implementations (JcrItemPropertySet) and/or by the  PropertyNameDecorator.
  • Resolve an item data source of complex fields, a functionality usually covered by item providers.
  • Manage item data sources of multi-value field entries. This is handled by the  MultiFormView.EntryResolution, which resolves the children and binds each of them to the item provider strategy.

...

info.magnolia.ui.form.field.transformer.*

In 6 UI
basic.BasicTransformerNot required and not used. Its functions are obsolete, ; some are taken over by Vaadin's concept of Vaadin PropertySet.
composite.CompositeTransformer

This behavior can be achieved by using the  info.magnolia.ui.editor.CurrentItemProvider and configuring the propertyNameDecorator property of the CompositeFieldDefinition.

composite.SwitchableTransformerinfo.magnolia.ui.editor.JcrChildNodeProvider

...

The 5 UI transformers with personalization-related functions have undergone the following changes, but still utilize use the old framework (magnolia-personalization-compatibility).

...