material-table VS react-table

Material-Table is a library that I used to use a lot. It was awesome. Unfortunately, the maintainer does not seem to be active on GitHub anymore, and the project is no longer being actively maintained. It went a couple of years without getting any updates, and there are some glaring NPM audit security warnings that you will receive if you install this in your project.

// https://github.com/mbrn/material-table/pull/2937#issuecomment-879017952 import MaterialTable, { MaterialTableProps } from 'material-table' import { TablePagination, TablePaginationProps } from '@material-ui/core' function PatchedPagination(props: TablePaginationProps) { const { ActionsComponent, onChangePage, onChangeRowsPerPage, ...tablePaginationProps } = props return ( { const { onPageChange, ...actionsComponentProps } = subprops return ( // @ts-expect-error ActionsComponent is provided by material-table ) }} /> ) } export default PatchedPagination

I'm trying to integrate react material-table (https://github.com/mbrn/material-table) with my project.

I'm using Material Table and I need change the Action column name but this column is automatic generated because I'm using editable function from material table.

okay more so like the exxample in here, https://www.npmjs.com/package/material-table

Ik like material table a lot. It's pretty easy to get started with and has great customization options.

The free offering is very lackluster, I currently roll my own editable table inspired by https://github.com/mbrn/material-table. The main reason was the inability to add frontend validation, but now it has a lot of functions that I need, each custom for my needs.

e.g: https://material-table.com/#/

5. react-table

I have a simple react-table with an expanded sub component whose data is tied to a Redux state object.

import ReactTable from 'react-table'...render() { return ( )} However, on their API Docs and examples, they all use useTable.

I have a functional component built around the React Table component that uses the Apollo GraphQL client for server-side pagination and searching. I am trying to implement debouncing for the searching so that only one query is executed against the server once the user stops typing with that value. I have tried the lodash debounce and awesome debounce promise solutions but still a query gets executed against the server for every character typed in the search field.