You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the /api/v1/stores?filter[location]=lat,long request will return up to 300 stores that are in a 5km radius from the provided lat long. This is a bit overwhelming for the applications to handle and probably to much for the users to parse through. So we are thinking of reducing the size of the response and return only the 100 stores that are close to the provided location.
If the user wants to see more locations they could move the map around and request for a slightly different location.
There are some potential concerns with discoverability, as in very populated places the users might not get the full list of stores. Some options are for the application to pass the store_type filter to the backend, for us to play a bit with the total number of stores returned, or in a future iteration paginate the results.
For now let's go with the backend change alone.
The text was updated successfully, but these errors were encountered:
Currently the
/api/v1/stores?filter[location]=lat,long
request will return up to 300 stores that are in a 5km radius from the provided lat long. This is a bit overwhelming for the applications to handle and probably to much for the users to parse through. So we are thinking of reducing the size of the response and return only the 100 stores that are close to the provided location.If the user wants to see more locations they could move the map around and request for a slightly different location.
There are some potential concerns with discoverability, as in very populated places the users might not get the full list of stores. Some options are for the application to pass the store_type filter to the backend, for us to play a bit with the total number of stores returned, or in a future iteration paginate the results.
For now let's go with the backend change alone.
The text was updated successfully, but these errors were encountered: