You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/09/01 14:40:00 UTC
[jira] [Commented] (NIFIREG-13) Initial implementation for registry
UI
[ https://issues.apache.org/jira/browse/NIFIREG-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150650#comment-16150650 ]
ASF GitHub Bot commented on NIFIREG-13:
---------------------------------------
GitHub user scottyaslan opened a pull request:
https://github.com/apache/nifi-registry/pull/8
[NIFIREG-13] Initial implementation of the registry UI/UX
You may view the FDS atomic component NgModule demo here: http://localhost:8080/nifi-registry/fluid-design-system
The initial NiFi Registry UI can be located at the following: http://localhost:8080/nifi-registry/explorer/grid-list/23f6cc59-0156-1000-06b4-2b0810089090
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/scottyaslan/nifi-registry devBranch
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-registry/pull/8.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #8
----
commit 53202c5f244c734a55b85bede99359642825f507
Author: Scott Aslan <sc...@gmail.com>
Date: 2017-09-01T14:23:16Z
[NIFIREG-13] Initial implementation of the registry UI/UX
----
> Initial implementation for registry UI
> --------------------------------------
>
> Key: NIFIREG-13
> URL: https://issues.apache.org/jira/browse/NIFIREG-13
> Project: NiFi Registry
> Issue Type: Sub-task
> Reporter: Scott Aslan
> Assignee: Scott Aslan
>
> This ticket is to implement a production ready build for an SPA that will eventually call the REST layer to request data. The SPA will:
> # Provide reuseable UI/UX components in the form (Fluid Design System NgModule)
> # Provide deep linking capabilities
> # Provide internationalization capability
> # Provide karma/Jasmine unit test harness (unit tests will be disabled be default)
> # Provide Protractor e2e test harness
> # Be theme-able (leveraging SASS and compiled at build time)
> # Use mock data instead of making actual REST calls
> # Be a rough draft of the UI/UX mocks provided in the parent ticket for this sub task.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)