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
This project currently uses a custom Conveyal library feature (woonerf’s fetch) as middleware to handle async logic/data fetching within action dispatches. Each call to fetch automatically dispatches another action to increment fetch state, which in turn updates a global pending state (this isLoading state functions as a global conditional for component display until load/state updates are complete). This causes issues as we implement new api calls and want to isolate the effects of a pending state to the component level (see PR #374). Switching to axios and replacing a global pending state dependent on the number of fetches will help us avoid this issue. In addition, we would be better served to replace fetch with axios for more intuitive data fetches and robust error handling.
The text was updated successfully, but these errors were encountered:
This project currently uses a custom Conveyal library feature (woonerf’s fetch) as middleware to handle async logic/data fetching within action dispatches. Each call to fetch automatically dispatches another action to increment
fetch
state, which in turn updates a global pending state (thisisLoading
state functions as a global conditional for component display until load/state updates are complete). This causes issues as we implement new api calls and want to isolate the effects of a pending state to the component level (see PR #374). Switching to axios and replacing a global pending state dependent on the number of fetches will help us avoid this issue. In addition, we would be better served to replace fetch with axios for more intuitive data fetches and robust error handling.The text was updated successfully, but these errors were encountered: