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
//*whether i use filteredData or actual appState we run into a recursive breakage. For now instead of seprating the data, we will try to manipulate appState directly, since same breakage occurs in both situations.
164
-
//* I suspect the appState and the changed data are in constant conflict with one another, and we might need to make changes in traverse when a toggle button is clicked. so all freshly new DOM data will have everything filtered upon arrival.
165
-
//* else newly arrived DOM data information on user's app will setState, then on update in our dev tool we'll rerun and change state.
166
-
//* best to have a toggle change a set of conditions in traverser, where if toggle is set to false, traverse and leave out these set of words apoloProvider etc.
167
-
//* filtering data after its already arrived with two traverse functions seem constly, and is the cause of our glitch.
168
-
//* throwing the filtering to dev and resetting appState is causing breakage, if cant find solution, go to the source of the issue, the traverser and set toggling conditions there.
169
-
// this.setState({
170
-
// filteredData: data
171
-
// });
172
-
this.setState({
173
-
appState: data
174
-
});
175
-
console.log(data,'filterOutComponents function ran successfully, filteredData is set to this object --coming from devtools line 169')
176
-
}
177
-
}
178
-
179
-
handleApolloFilter(arr){
180
-
//* if first index of arr is not in componentsToFilter arr, set incoming array to componentsToFilter
0 commit comments