The goal would be to introduce the feature pagination into the webapp based on the api-server implementation
This PR is work in progress - I stopped working on that since I'm not that familiar with frontend development.
Especially since currently the approach is: retrieving all data e.g accounts - then filter that in the current state.
This should be changed to only retrieve the data that is required, and in case. eg. checking for the availability of a property in the collection - there is a dedicated function in the api-server
Instead of listing all applications to check if the name is available and can be created, call
The goal would be to introduce the feature pagination into the webapp based on the api-server implementation
This PR is work in progress - I stopped working on that since I'm not that familiar with frontend development. Especially since currently the approach is: retrieving all data e.g accounts - then filter that in the current state.
This should be changed to only retrieve the data that is required, and in case. eg. checking for the availability of a property in the collection - there is a dedicated function in the api-server
Instead of listing all applications to check if the name is available and can be created, call
/:sid/Accounts/Availability?type=name&value=${value}This PR adds pagination to:
With the environment variable
PAGINATION: truethe feature can be enabled.