You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Scott Aslan (JIRA)" <ji...@apache.org> on 2019/06/06 16:01:00 UTC

[jira] [Commented] (NIFI-6249) UI - Provide nifi-fds es6 modules that require no aliasing of nifi-fds directory structure.

    [ https://issues.apache.org/jira/browse/NIFI-6249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857826#comment-16857826 ] 

Scott Aslan commented on NIFI-6249:
-----------------------------------

We will need to update the Demo application sample code to demonstrate ES6 imports etc too.

> UI - Provide nifi-fds es6 modules that require no aliasing of nifi-fds directory structure.
> -------------------------------------------------------------------------------------------
>
>                 Key: NIFI-6249
>                 URL: https://issues.apache.org/jira/browse/NIFI-6249
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: FDS
>            Reporter: Robert Fellows
>            Assignee: Robert Fellows
>            Priority: Major
>
> nifi-fds uses aliases in some/many import/require statements that force consumers of the package to also alias them. This adds a complexity to the configuration that could be mitigated for ES6 consumers. The ideal solution would allow consuming apps to install @nifi-fds/core and then import it's modules without needing to know anything internally to how nifi-fds is structured.
> Examples might look something like this...
> {noformat}
> import { FdsCoreModule } from '@nifi-fds/core'
> // or
> import { FdsDialogService, FdsSnackBarService, FdsCoasterComponent } from '@nifi-fds/core'
> {noformat}
> Also, update the README to reflect updates.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)