[
https://issues.apache.org/jira/browse/NIFI-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15287854#comment-15287854
]
ASF GitHub Bot commented on NIFI-1850:
--------------------------------------
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.
> JSON-to-JSON Schema Converter Editor
> ------------------------------------
>
> Key: NIFI-1850
> URL: https://issues.apache.org/jira/browse/NIFI-1850
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core UI
> Reporter: Yolanda M. Davis
> Priority: Minor
> Fix For: 1.0.0, 0.7.0
>
>
> With NIFI-361 implemented, users can embed a JOLT spec into the TransformJSON
> processor. However, building the spec is not intuitive enough without the
> ability to obtain real time feedback on spec syntax and preview output data.
> Would like to have a specification editor and transform preview view added
> to the processor configuration screen to allow users to immediately see the
> impact on the output JSON data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
