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
While starting the docs locally an error appears if you switch between JS and TS display in the DataGrid chapters.
It seems the overall functionality is not affected, but you see an overlay error message and tracebacks in the console.
The issue is present in the latest release.
I have searched the issues of this repository and believe that this is not a duplicate.
Current Behavior 😯
An error appears if you switch between JS and TS display in the DataGrid chapters (e.g. in filtering).
useFilter.ts?8d40:74 Uncaught TypeError: Cannot read property 'getApplyFilterFn' of undefined
at Object.eval [as applyFilter] (useFilter.ts?8d40:74)
at EventEmitter.apiRef.current.<computed> [as applyFilter] (useApiMethod.ts?129e:27)
at eval (useFilter.ts?8d40:127)
at Array.forEach (<anonymous>)
at eval (useFilter.ts?8d40:126)
at eval (useFilter.ts?8d40:173)
at eval (useFilter.ts?8d40:253)
at Array.forEach (<anonymous>)
at Object.eval [as setFilterModel] (useFilter.ts?8d40:253)
at EventEmitter.apiRef.current.<computed> [as setFilterModel] (useApiMethod.ts?129e:27)
at eval (useFilter.ts?8d40:293)
at commitHookEffectListMount (react-dom.development.js?f8c1:19731)
at commitPassiveHookEffects (react-dom.development.js?f8c1:19769)
at HTMLUnknownElement.callCallback (react-dom.development.js?f8c1:188)
at HTMLUnknownElement.dispatchEvent (<anonymous>)
at Object.invokeGuardedCallbackDev (react-dom.development.js?f8c1:237)
at invokeGuardedCallback (react-dom.development.js?f8c1:292)
at flushPassiveEffectsImpl (react-dom.development.js?f8c1:22853)
at unstable_runWithPriority (scheduler.development.js?bacd:653)
at runWithPriority$1 (react-dom.development.js?f8c1:11039)
at flushPassiveEffects (react-dom.development.js?f8c1:22820)
at performSyncWorkOnRoot (react-dom.development.js?f8c1:21737)
at eval (react-dom.development.js?f8c1:11089)
at unstable_runWithPriority (scheduler.development.js?bacd:653)
at runWithPriority$1 (react-dom.development.js?f8c1:11039)
at flushSyncCallbackQueueImpl (react-dom.development.js?f8c1:11084)
at flushSyncCallbackQueue (react-dom.development.js?f8c1:11072)
at discreteUpdates$1 (react-dom.development.js?f8c1:21893)
at discreteUpdates (react-dom.development.js?f8c1:806)
at dispatchDiscreteEvent (react-dom.development.js?f8c1:4168)
eval @ useFilter.ts?8d40:74
apiRef.current.<computed> @ useApiMethod.ts?129e:27
eval @ useFilter.ts?8d40:127
eval @ useFilter.ts?8d40:126
eval @ useFilter.ts?8d40:173
eval @ useFilter.ts?8d40:253
eval @ useFilter.ts?8d40:253
apiRef.current.<computed> @ useApiMethod.ts?129e:27
eval @ useFilter.ts?8d40:293
commitHookEffectListMount @ react-dom.development.js?f8c1:19731
commitPassiveHookEffects @ react-dom.development.js?f8c1:19769
callCallback @ react-dom.development.js?f8c1:188
invokeGuardedCallbackDev @ react-dom.development.js?f8c1:237
invokeGuardedCallback @ react-dom.development.js?f8c1:292
flushPassiveEffectsImpl @ react-dom.development.js?f8c1:22853
unstable_runWithPriority @ scheduler.development.js?bacd:653
runWithPriority$1 @ react-dom.development.js?f8c1:11039
flushPassiveEffects @ react-dom.development.js?f8c1:22820
performSyncWorkOnRoot @ react-dom.development.js?f8c1:21737
eval @ react-dom.development.js?f8c1:11089
unstable_runWithPriority @ scheduler.development.js?bacd:653
runWithPriority$1 @ react-dom.development.js?f8c1:11039
flushSyncCallbackQueueImpl @ react-dom.development.js?f8c1:11084
flushSyncCallbackQueue @ react-dom.development.js?f8c1:11072
discreteUpdates$1 @ react-dom.development.js?f8c1:21893
discreteUpdates @ react-dom.development.js?f8c1:806
dispatchDiscreteEvent @ react-dom.development.js?f8c1:4168
21:41:38.226
Expected Behavior 🤔
Switching between JS and TS display should work without any errors
I compared with the live hosted version and there it seems to be fine.
It might be an issue of the dev environment.
Context 🔦
I ran into this issue while working on the changes submitted in #973.
First I thought that this was related to my own changes, but I was able to reproduce it on master.
While starting the docs locally an error appears if you switch between JS and TS display in the DataGrid chapters.
It seems the overall functionality is not affected, but you see an overlay error message and tracebacks in the console.
Current Behavior 😯
An error appears if you switch between JS and TS display in the DataGrid chapters (e.g. in filtering).
Expected Behavior 🤔
Switching between JS and TS display should work without any errors
Steps to Reproduce 🕹
Steps:
I compared with the live hosted version and there it seems to be fine.
It might be an issue of the dev environment.
Context 🔦
I ran into this issue while working on the changes submitted in #973.
First I thought that this was related to my own changes, but I was able to reproduce it on master.
Your Environment 🌎
`npx @material-ui/envinfo`
Let me know if you need any other info :)
The text was updated successfully, but these errors were encountered: