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, if you try to select a date range on dev.311-data.org, nothing happens.
It looks like there has been a lot of work to manage the startDate and endDate for the DateSelector in Redux, see PR #1108. However, it seems like the RequestsLayer is not listening for updates on the startDate and endDate. E.g., if the ncBoundaries are updated, the Map will reinitialize the ncLayer given the new NC.
The text was updated successfully, but these errors were encountered:
To efficiently pull only the data that we need in the case that the user wants to change the date range, we'll also need to track the date range(s) of our request data in the store: it will be initialized to be an array containing one element, which is the date range for the previous week, e.g., [("2022-06-22", "2022-06-29")]. If the user wants to change the date range to be only ("2022-06-29", "2022-06-29") (i.e., only today), then we can check if the date ranges in our store totally contain this new selected date range. In this case, it does, so we don't need to pull any more data, and we can simply update the filter to the new selected date range.
In the case that the selected date range is NOT completely contained within our store's date ranges, we will need to make a new API request for the difference. Then, we'll need to update our store's date ranges to include the date range, and set the filter.
Currently, if you try to select a date range on dev.311-data.org, nothing happens.
It looks like there has been a lot of work to manage the startDate and endDate for the DateSelector in Redux, see PR #1108. However, it seems like the RequestsLayer is not listening for updates on the startDate and endDate. E.g., if the ncBoundaries are updated, the Map will reinitialize the ncLayer given the new NC.
The text was updated successfully, but these errors were encountered: