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
{{ message }}
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.
After some extensive testing, I have determined that managing filters purely via React state is not a viable approach since data will be lost as soon as you proceed to the next page, and data from the pageContext object is a single direction data flow.
My proposed solution is instead of having the filters be buttons, where clicking them changes state, it makes more sense for them to be links to pages that use the URL params and queries to that can be used to map data onto the page. This will require some experimentation on my part in the interest of satisfying other requirements like issue #82 and #83
The text was updated successfully, but these errors were encountered:
After some extensive testing, I have determined that managing filters purely via React state is not a viable approach since data will be lost as soon as you proceed to the next page, and data from the pageContext object is a single direction data flow.
My proposed solution is instead of having the filters be buttons, where clicking them changes state, it makes more sense for them to be links to pages that use the URL params and queries to that can be used to map data onto the page. This will require some experimentation on my part in the interest of satisfying other requirements like issue #82 and #83
The text was updated successfully, but these errors were encountered: