Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update best-practices.mdx #1098

Merged
merged 1 commit into from Apr 16, 2024
Merged

Update best-practices.mdx #1098

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion apps/material-react-table-docs/pages/docs/guides/best-practices.mdx
View file
Open in desktop
Expand Up @@ -297,7 +297,7 @@ export const CustomMRTTable = <TData extends MRT_RowData>({

By using the `TData` generic correctly, you can maintain type-safety in your re-usable component that will adapt to different types of data you will have throughout your application.

Though, be aware that the weakness of this is approach is that it will be more annoying to get access to the `table` instance or read table state where you need it.
Though, be aware that the weakness of this approach is that it will be more annoying to get access to the `table` instance or read table state where you need it.

When re-using your MRT table component, it will just look something like this:

Expand Down