[ 
https://issues.apache.org/jira/browse/NIFIREG-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kevin Doran updated NIFIREG-68:
-------------------------------
    Description: 
Currently, there is a lot of frontend UI/UX that does not map cleanly to the 
REST API backend, creating the need for lots of logic in the front end. This 
complicates the frontend code and also makes it non-intuitive for third parties 
how to use the REST API to accomplish actions that can be performed in the UI.

This ticket is to explore and implement ways to move some of the frontend logic 
into the backend to replace inferred fields with values that can be directly 
read. Also replace one-to-many frontend/backend mappings with one-to-one 
mappings.

  was:
Currently, there is a lot of frontend UI/UX that does not map cleanly to the 
REST API backend, creating the need for lots of logic in the front end. This 
complicates the frontend code and also makes it non-intuitive for third parties 
how to use the REST API to accomplish actions that can be performed in the UI.

This ticket is to explore and implement ways to move some of the frontend logic 
into the backend to replace inferred fields with values that can be directly 
performed. Also replace one-to-many frontend/backend mappings with one-to-one 
mappings.


> Align frontend-backend models and actions
> -----------------------------------------
>
>                 Key: NIFIREG-68
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-68
>             Project: NiFi Registry
>          Issue Type: Improvement
>            Reporter: Kevin Doran
>            Assignee: Kevin Doran
>
> Currently, there is a lot of frontend UI/UX that does not map cleanly to the 
> REST API backend, creating the need for lots of logic in the front end. This 
> complicates the frontend code and also makes it non-intuitive for third 
> parties how to use the REST API to accomplish actions that can be performed 
> in the UI.
> This ticket is to explore and implement ways to move some of the frontend 
> logic into the backend to replace inferred fields with values that can be 
> directly read. Also replace one-to-many frontend/backend mappings with 
> one-to-one mappings.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to