Releases: jbetancur/react-data-table-component
v1.4.0
This version
- Extend Theming support
- Memoize theme so it does not merge on every re-render
- Add Theme demo examples
Breaking change
- default theme contextMenu theme was moved out of the `header https://github.com/jbetancur/react-data-table-component/blob/61e6915e44f8afe47987905bd6caff402a9c47fd/src/themes/default.js#L13
Fixed in 1.3.0 (catching up release notes)
- Memoize sorting Closes #65
- Cleans up superfluous state props
- fix decorate columns - was not being called. decorate columns mainly assigns unique keys to columns items
- fix context header animations
v1.2.0
v1.1.0
v1.0.1
v1.0.0
This is a GA release includes built-in pagination as well as some under the hood improvements.
- 💥 Pagination feature
- Upgrade to React 16.3
- Migrate functionality to React. Context
- remove lifecycle polyfills
- convert to pure/functional/memoization where it made sense
- Unit/Integration testing
- ❤️ Migrate away from enzyme to react-testing-library
- Add missing test cases
- General clean up docs/code
For more info see https://github.com/jbetancur/react-data-table-component/milestone/1?closed=1
v0.13.0
Bugs Fixes
- Fixed issue where if underlying data was changed and the table data is sorted, that the table would revert back to the default sorted state.
- Prevent re-renders on data change using deep equal.
Enhancements
- Adds small amount of top/bottom row padding to rows
- Bolder font for sort focus
v0.11.0
Bug Fixes
- Prop Types warnings fixed for [TableHeader] actions/contextActions
Potential Breaking Changes
- REMOVED TableHeader actions being hidden when
progessPending
is false. It was decided to keep the onus on the API user instead of the library as this offers created control
v0.10.0
v0.9.1
Release Notes
Bugs
- #26 Unable to select text in a cell.
Known Issues
As described in #26 React data table is unable to allow text selection when the onRowClicked
callback is set. Therefore, as a workaround when the property is not set then the table will behave normally and allow text selection.
IMHO/Experience, clicking/touching rows to navigate is a terrible UX for Desktop apps since the functionality is not immediately obvious to a user. Probably, the right way to do this is to have a More Detail Button or use an Edit action on a menu, or even to make a field link/clickable that invokes some action or navigation. However, there are cases when this behavior is the norm and so the workaround if you want to allow TableCell selection is to not use onRowClicked