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

Clean up code to only use the isPlugin approach

    XMLWordPrintable

    Details

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

      Description

      We decided to take the isPlugin approach and use the plugin class as the template's plugin.class, instead of using the built-in PropertyFieldPlugin.

      Currently the code is in experimental mode and supports both approaches. We also bootstrap 2 different namespaces to be able to test the 2 approaches.

      Clean up the code: remove support for the PropertyFieldPlugin approach.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: