react-vt-table icon indicating copy to clipboard operation
react-vt-table copied to clipboard

Running react-vt-table on Reacat 17.x

Open atompie opened this issue 2 years ago • 0 comments

Running react-tv-table on react 17.x throws the following warnings an errors:

Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://reactjs.org/link/unsafe-component-lifecycles for details.

* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://reactjs.org/link/derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 18.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Draggable
Warning: componentWillUpdate has been renamed, and is not recommended for use. See https://reactjs.org/link/unsafe-component-lifecycles for details.

* Move data fetching code or side effects to componentDidUpdate.
* Rename componentWillUpdate to UNSAFE_componentWillUpdate to suppress this warning in non-strict mode. In React 18.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Table
Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of Draggable which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here: https://reactjs.org/link/strict-mode-find-node
div
DraggableCore@http://localhost:3000/static/js/bundle.js:199250:21
Draggable@http://localhost:3000/static/js/bundle.js:199628:21
ColumnResizer@http://localhost:3000/static/js/bundle.js:689849:35
div
div
Header@http://localhost:3000/static/js/bundle.js:689896:29
div
Table@http://localhost:3000/static/js/bundle.js:690228:30
div
AutoSizer@http://localhost:3000/static/js/bundle.js:689630:19
__WEBPACK_DEFAULT_EXPORT__@http://localhost:3000/static/js/bundle.js:22831:7
div
TryOut
Route@http://localhost:3000/static/js/bundle.js:682879:29
div
div
MainContent@http://localhost:3000/static/js/bundle.js:976:7
AppBox
Route@http://localhost:3000/static/js/bundle.js:682879:29
PrivateRoute@http://localhost:3000/static/js/bundle.js:1229:7
Switch@http://localhost:3000/static/js/bundle.js:683081:29
Router@http://localhost:3000/static/js/bundle.js:682510:30
BrowserRouter@http://localhost:3000/static/js/bundle.js:682132:35
App@http://localhost:3000/static/js/bundle.js:350:7
ConnectFunction@http://localhost:3000/static/js/bundle.js:678800:68
ConfirmProvider@http://localhost:3000/static/js/bundle.js:161744:18
InnerThemeProvider@http://localhost:3000/static/js/bundle.js:69986:70
ThemeProvider@http://localhost:3000/static/js/bundle.js:68831:7
ThemeProvider@http://localhost:3000/static/js/bundle.js:70008:7
StyledEngineProvider@http://localhost:3000/static/js/bundle.js:69016:7
Provider@http://localhost:3000/static/js/bundle.js:678512:15

Is there any chance of getting rid of this? Thanks, and the library is great :)

atompie avatar Feb 08 '22 12:02 atompie