Uploaded image for project: '[Read Only] - Hippo Plugins'
  1. [Read Only] - Hippo Plugins
  2. HIPPLUG-1631

Try removing the need for interface org.hippoecm.frontend.editor.plugins.field.ConfigurableFieldPlugin

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Low
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: plugins-taxonomy
    • Labels:
      None
    • Similar issues:
    • Processed by team:
      Pulsar
    • Sprint:
      Platform 226 - Taxonomy 1, Platform 227 - Taxonomy 2, Pulsar 228 - Field Types

      Description

      Interface org.hippoecm.frontend.editor.plugins.field.ConfigurableFieldPlugin is used to mark a RenderPlugin as one that needs properties to be shown in the doctype editor, when user clicks on a field, see attachment

      This is used in org.hippoecm.frontend.editor.builder.PreviewClusterConfig#getPluginConfigEditorClass to make sure we get a FieldPluginEditorPlugin, this is the plugin for rendering the properties. This entails that custom plugins need to implement this interface (plugin org.onehippo.taxonomy.plugin.TaxonomyPickerPlugin does so).

      Investigate if we can ommit this interface: ideally you can access the field descriptor for this field and check if isPlugin(). If so, a plugin that renders properties should be selected (like the FieldPluginEditorPlugin). As far as I've seen it is not possible to access the field descriptor cause this code is running inside a plugin cluster that is unaware of the nodetypes.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mchatzidakis Minos Chatzidakis
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: