[Refactoring, Cockpit] - Move non-standard plugin interfaces into 'properties' object

XMLWordPrintable

      We have many Plugin points, which need more than the default configuration. To keep the interface tidy, we should avoid polluting the root object with these values.

      AT

      • All non-standard Configs are moved into arguments object.
      • The Examples are adjusted
      • All Plugin points use the same interface: 
        {
  id: "customPlugin",
  pluginPoint: "cockpit.dashboard",
  priority: 5,
  render: container => {
    container.innerHTML = "Hello World!";
  },
  unmount: () => {},
  properties: {}
}

      Note that the label property will also move into arguments.

      =========

      Make it easier to access the camundaAPI

      AT

      • the arguments of the render function always contain a api object with the endpoints
      • Examples are adjusted

        This is the controller panel for Smart Panels app

              Assignee:
              Hariharan Parasuraman
              Reporter:
              Martin Stamm
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: