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
When defining columns for table, I am getting missing props validation from ESlint (first screenshoot). It occuried in earlier beta versions of v1 as well, but it can be turned of by using /* eslint-disable react/prop-types */. Is this bug related to ESlint or table? I have latest version of ESlint, Prettier as well as TypeScript.
Another ESlint warning is react/no-unstable-nested-components (second screenshoot), which can be turned off by last rule in ESlint config I attached.
Basically it complains about React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state. But I need to use some data from hooks, use them to render component for Cell, so I dont know how to do that properly. Is this the right way tho and ESlint just trying to warn me or is this a bad way to do it? I just followed your examples .
Minimal, Reproducible Example - (Optional, but Recommended)
Described above
Screenshots or Videos (Optional)
Do you intend to try to help solve this bug with your own PR?
None
Terms
I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
The text was updated successfully, but these errors were encountered:
mantine-react-table version
v1.0.0
react & react-dom versions
v18.2.0
Describe the bug and the steps to reproduce it
When defining columns for table, I am getting
missing props validation
fromESlint
(first screenshoot). It occuried in earlier beta versions of v1 as well, but it can be turned of by using/* eslint-disable react/prop-types */
. Is this bug related to ESlint or table? I have latest version of ESlint, Prettier as well as TypeScript.Another ESlint warning is
react/no-unstable-nested-components
(second screenshoot), which can be turned off by last rule in ESlint config I attached.Basically it complains about
React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state.
But I need to use some data from hooks, use them to render component for Cell, so I dont know how to do that properly. Is this the right way tho and ESlint just trying to warn me or is this a bad way to do it? I just followed your examples .Here are my columns:
Here is rendered component for Cell:
Here is ESlint config:
Minimal, Reproducible Example - (Optional, but Recommended)
Described above
Screenshots or Videos (Optional)
Do you intend to try to help solve this bug with your own PR?
None
Terms
The text was updated successfully, but these errors were encountered: