Denis GARET (AmeXio) created NIFI-15708:
-------------------------------------------
Summary: [Advanced UI]
Key: NIFI-15708
URL: https://issues.apache.org/jira/browse/NIFI-15708
Project: Apache NiFi
Issue Type: Improvement
Components: Core UI
Affects Versions: 2.8.0
Reporter: Denis GARET (AmeXio)
*As* a developer extending NiFi with extra capabilities
*I want to* be provided with helpers / integrated mechanisms
*In order to* ease building Advanced UIs for custom components (keeping overall
UX consistency)
My specific concern is around the way *NiFi theme* is injected into advanced
UIs.
* The "nifi-frontend" module provides valuable assets to be reused across
various "Advanced UIs for custom components" (as it is the case for OOTB
Advanced UIs such as UpdateAttribute or JOLTTransformJSON)
* In order to keep overall UI/Theme consistent for other advanced UIs I plan
to leverage such elements
* At the time being I did not find a proper way to achieve this rather than
copy/pasting existing "source code files" (subfolder
src/main/frontend/libs/shared from module nifi-frontend into my own
repository/modules
Would there be another way to achieve this objective of keeping UX/Theme
consistent when developing addintional Advanced UIs for custom components ?
(I may have missed some documented instructions/hints to setup an alternate
strategy)
Aternatively, would it be possible to consider anticipating smoother extension
mechanisms for Advanced UIs such as
* (ideal) Exposing the @nifi/shared package/bundle in order to make it
reusable in other Advanced UIs (my understanding being that it is currently
only available locally when building the nifi-frontend module
* (acceptable workaround that would require less effort I guess) Adapt
configuation applicable for the maven-source-plugin on module nifi-frontend in
order to have the associated publishedjar (nifi-frontend-<version>-sources.jar)
contain frontend source files (I guess the default plugin configuration makes
it ignore non java files) so that custom developments could reuse it through
maven-dependency-plugin
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
