Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/424#issuecomment-219881237
@YolandaMDavis Yep. We're definitely on the same page here. However, we
currently have not formally established any APIs/components/widgets for UI
extensions to consume. Because of this I think we're ok. In this case
referencing stuff bundled in nifi-web-ui is fair game with the understanding
that they may change with any release. During that release would we would also
need to update this custom UI appropriately.
Going forward, we should establish APIs/components/widgets for custom UIs
to consume with guarantees around their APIs. However, we need to be mindful
that when we do this we won't be able to freely break those APIs. I would
prefer to decouple these from any particular framework/versions so we're not
'stuck' with anything. We can obviously discuss this in more details as custom
UIs become more prominent.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
