Since when the number of routes saved by the user grows the time it takes to retrieve them from the POD grows exponentially, a new mechanism has to be implemented to palliate this. First of all, instead of sending the requests one by one, they should be sent all at the same time, making good use of Javascript asynchronous capabilities. Second, some kind of pagination has to be implemented, retrieving a low number of routes each time, and giving the user an option to get more routes.
Expected behaviour: The routes are retrieved in batches and the user can choose to get more.
Other development information, extensions and problems: none
Acceptance criteria
[ ] Change the listing of routes to send the requests and process them all at the same time.
[ ] Add a paging mechanism to the route cache and the route retrieving system.
[ ] Add an option in the list of routes view to get more routes.
Testing scenarios
[ ] When requesting more routes, if there's no more routes none are retrieved (no calls are made) and the interface shows it accordingly.
Feature description 🗺️
Since when the number of routes saved by the user grows the time it takes to retrieve them from the POD grows exponentially, a new mechanism has to be implemented to palliate this. First of all, instead of sending the requests one by one, they should be sent all at the same time, making good use of Javascript asynchronous capabilities. Second, some kind of pagination has to be implemented, retrieving a low number of routes each time, and giving the user an option to get more routes.
Expected behaviour: The routes are retrieved in batches and the user can choose to get more.
Other development information, extensions and problems:
noneAcceptance criteria
Testing scenarios
Linked pull requests