You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Andrea Patricelli (JIRA)" <ji...@apache.org> on 2017/02/01 15:21:51 UTC

[jira] [Updated] (SYNCOPE-1005) Schema sorting should be done on JS side

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

Andrea Patricelli updated SYNCOPE-1005:
---------------------------------------
    Description: 
Currently sorting of schemas (by name) is done on Java side in SchemaResource.java class.
Move sorting of schema on JS side. UserContorller.js or schemaService.js should be the right place.
This will improve the customizability of sorting of user Plain/Derived/Virtual attributes.

  was:
Currently sorting of schemas (by name) is done on Java side in `SchemaResource.java` class.
Move sorting of schema on JS side. UserContorller.js or schemaService.js should be the right place.
This will improve the customizability of sorting of user Plain/Derived/Virtual attributes.


> Schema sorting should be done on JS side 
> -----------------------------------------
>
>                 Key: SYNCOPE-1005
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1005
>             Project: Syncope
>          Issue Type: Improvement
>          Components: enduser
>    Affects Versions: 2.0.2
>            Reporter: Andrea Patricelli
>            Assignee: Andrea Patricelli
>            Priority: Minor
>             Fix For: 2.0.3, 2.1.0
>
>
> Currently sorting of schemas (by name) is done on Java side in SchemaResource.java class.
> Move sorting of schema on JS side. UserContorller.js or schemaService.js should be the right place.
> This will improve the customizability of sorting of user Plain/Derived/Virtual attributes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)