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

Sandor Molnar updated KNOX-2104:
--------------------------------
    Description: 
As part of KNOX-2056, there was a need to introduce {{angular2-datatable}} in 
order to display Knox resources (topologies, service definitions, etc..) in a 
paginated table if needed (>10 resources found).
As [~lmccay] indicated in one of [his review 
comments|https://github.com/apache/knox/pull/173#pullrequestreview-310015043] 
the pagination has been reset every time a service definition got 
updated/removed. It'd be nice to stay on the same page.

  was:
As part of KNOX-2056, there was a need to introduce {{angular2-datatable}} in 
order to display Knox resources (topologies, service definitions, etc..) in a 
paginated table if needed (>10 resources found).
As [~lmccay] indicated in one of his review comments the pagination has been 
reset every time a service definition got updated/removed. It'd be nice to stay 
on the same page.


> Admin UI should display the same page after successful resource operation
> -------------------------------------------------------------------------
>
>                 Key: KNOX-2104
>                 URL: https://issues.apache.org/jira/browse/KNOX-2104
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: AdminUI
>    Affects Versions: 1.4.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Minor
>             Fix For: 1.4.0
>
>
> As part of KNOX-2056, there was a need to introduce {{angular2-datatable}} in 
> order to display Knox resources (topologies, service definitions, etc..) in a 
> paginated table if needed (>10 resources found).
> As [~lmccay] indicated in one of [his review 
> comments|https://github.com/apache/knox/pull/173#pullrequestreview-310015043] 
> the pagination has been reset every time a service definition got 
> updated/removed. It'd be nice to stay on the same page.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to