nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFIREG-13) Initial implementation for registry UI
Date Tue, 05 Sep 2017 17:15:00 GMT

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

ASF GitHub Bot commented on NIFIREG-13:
---------------------------------------

Github user mcgilman commented on the issue:

    https://github.com/apache/nifi-registry/pull/8
  
    The PR is a great starting point for the registry front end. Obviously, there is some
work remaining to get the front end and back end integrated but we can file subsequent JIRAs
for that effort and coordinate that work among the relevant contributors. 
    
    Also a couple more general comments:
    
    - We'll need to figure out where the fluid design system will live and then move the demo
application with it. I do not believe it belongs as part of the registry front end. But, let's
file a follow-on JIRA for this effort.
    - There appears to be some delay when loading the page for the first time. Let's file
another follow-on JIRA to investigate further and possibly add a loading screen.
    
    Let's address a few of the smaller items mentioned here and get this merged so we can
continue with the integration effort while looking into a few of the larger term items which
we'll file follow-on JIRAs for.
    
    Thanks again @scottyaslan!


> 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)

Mime
View raw message