myzenwallet
myzenwallet copied to clipboard
Bump react-table from 6.11.5 to 7.7.0
Bumps react-table from 6.11.5 to 7.7.0.
Release notes
Sourced from react-table's releases.
v7.7.0
7.7.0 (2021-04-25)
Features
v7.6.3
7.6.3 (2021-01-11)
Bug Fixes
- provide parentRows and data to accessor (f97fb98)
v7.6.2
7.6.2 (2020-11-13)
Bug Fixes
v7.6.1
7.6.1 (2020-10-26)
Bug Fixes
v7.6.0
7.6.0 (2020-10-10)
Bug Fixes
- utils: Add recently removed export statement (#2764) (a9b57eb)
- bug in sort subRows data and add test in useSortBy (#2633) (3cba528)
- useFlexLayout: change table min width to be the sum of min width of all columns (#2639) (d37856f)
- useRowSelect: change to toggleRowSelected reducer to use the previous state (#2651) (1d92c6d), closes #2171
- useRowSelect: verify row selection based on reducer state (#2666) (0c452eb)
- useRowState: change argument for "initialRowStateAccessor" and "initialCellStateAccessor" (#2719) (188a392), closes #1812 #2102 #2701 #2102 #2701
- virtualized-rows: header/body column aligment (#2711) (9f4383b)
- useExpanded - utils update (#2738) (bd90f10)
Features
... (truncated)
Changelog
Sourced from react-table's changelog.
React Table Changelog
7.0.5
- Added semantic release support. So no more changelog entries here - see Releases instead! See ya!
7.0.4
- Fixed a regression where
@scarf/scarf
was somehow removed from the package dependencies7.0.3
- Fixed an issue where unnecessary documentation dependencies were added when installing the library
- Fixed an issue where the
scripts
directory was not added to the npm package on build7.0.2
- Fixed an issue where the internal flexRenderer would not work correctly in production due to the strangest friggin' minification bug I've ever encountered. 🤷♂️
7.0.1
- Added the
value
property to cell renderers so that destructurin the value from thecell
property is now not necessary. This should help with people migrating from v6 and also just to cut down on noise in cell renderers- Fixed an issue where rollup would not build correctly
- Fixed an issue where a page index of
-1
would result in an error7.0.0 🎉
- Fixed an issue where page options array could be empty
- Fixed an issue where duplicate columns would be silently deduped. There is now a warning when duplicate columns are found based on their IDs
- Moved some functions around so they will get treeshaked with their respective plugins that use them.
- Fixed an issue where filters, sorting, or grouping changes would not reset pagination
- Added table and column level options for disabling global filters
- Fixed an issue where row selection was not deselecting rows
- Fixed an issue where flex table rendering was not giving the table a minimum width with necessary
- Fixed an issue where row selection would not work when using other row-transformative plugins like filters or grouping
- Fixed an issue where header groups were not memoized correctly
7.0.0-rc.16
- Moved away from snapshot tests. No more testing implementation details.
- Added
visibleColumns
andvisibleColumnsDeps
hooks to manipulate columns after all data is processed. Further visibility processing may result in these columns not being visible, such ashiddenColumn
state- The
useRows
hook has been deprecated due to its dangerous nature 💀- Added the
instance.rowsById
object- Renamed
instance.flatColumns
toinstance.allColumns
which now accumulates ALL columns created for the table, visible or not.- Added the
instance.visibleColumns
object- Fix an issue where
useAsyncDebounce
would crash when passed arguments- Started development on the
usePivotColumns
plugin, which can be tested currently using the_UNSTABLE_usePivotColumns
export.- Renamed
cell.isRepeatedValue
tocell.isPlaceholder
- Removed
useConsumeHookGetter
as it was inefficient most of the time and noisy- All hooks are now "consumed" right after main plugin functions are run. This means that any attempt to add a plugin after that will result in a runtime error (for good reason, since using hook points should not be a conditional or async operation)
... (truncated)
Commits
- See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -
@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language -
@dependabot badge me
will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot dashboard:
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)