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/07/22 21:27:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Scott Aslan updated NIFI-6249:
------------------------------
Fix Version/s: fds-0.2
> 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
> Fix For: fds-0.2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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.14#76016)