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, using this endpoint only the area mappings of the tally sheet listings are taken care of. Consequently, it has so many redundant data.
I propose, let's make the area get all endpoint to take a list of areaIds and a list of parentAreaIds. So, that based on the tally sheet listing, we could retrieve the required list of mappings only.
I see following tasks in high level.
Enable the additional parameters in area get all.
Adding a service provider [1]for areas in front end.
Replace all the instanced in the frontend where areaMap is used.
Currently, using this endpoint only the area mappings of the tally sheet listings are taken care of. Consequently, it has so many redundant data.
I propose, let's make the area get all endpoint to take a list of areaIds and a list of parentAreaIds. So, that based on the tally sheet listing, we could retrieve the required list of mappings only.
I see following tasks in high level.
[1] https://github.com/ECLK/results-tabulation/tree/master/results-tabulation-ui/src/services
The text was updated successfully, but these errors were encountered: