Why are getCoreRowModel, onStateChange and renderFallbackValue required?
#303
-
|
I'm sure there is a good reason for these props to be required. But if I'm able to create a material react table component just fine without specifying these attributes (except for some linting errors), it poses the question: are these actually required? Or are they just another good practice or convention that should be followed? If it's the latter, then in my opinion (and I'm open to other perspectives) they shouldn't be a required prop, but we should stress somewhere in the documentation the importance of configuring these correctly. Mainly because if, for example, we're prototyping something and we just want to knock up a simple table, we might not be concerned about the best way of doing things, but just about doing things quickly. What are peoples thoughts on this? |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
|
They are not required in MRT, they just required internally in the lib for react table. Where are you seeing this? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
If you are using Webstorm and this happens: Just wrap a Partial around MaterialReactTableProps like this: |
Beta Was this translation helpful? Give feedback.

If you are using Webstorm and this happens: Just wrap a Partial around MaterialReactTableProps like this:
Partial<MaterialReactTableProps>