Skip to content
This repository has been archived by the owner on Jan 13, 2022. It is now read-only.

Releases: facebookarchive/fixed-data-table

v0.6.0

14 Nov 01:02
Compare
Choose a tag to compare

The FixedDataTable v0.6 release deprecated a large number of APIs in an effort to simplify its use and increase flexibility. The changes come under two major areas, customisable cell rendering and flexible data sources.

More details about migration of API can be found here: http://facebook.github.io/fixed-data-table/v6-migration.html

v0.5.0

28 Oct 19:34
Compare
Choose a tag to compare

React 0.14 support!

v0.4.7

30 Sep 21:56
Compare
Choose a tag to compare

Support for [email protected] +

v0.4.6

17 Aug 23:23
Compare
Choose a tag to compare

Add support for React 0.14.0-beta3.

v0.4.5

17 Aug 22:37
Compare
Choose a tag to compare

Fixes a problem with webpack configs and the inclusion of react-for-atom.

React-for-atom is not included in this release, so atom is no longer supported directly.

v0.4.4

13 Aug 00:02
Compare
Choose a tag to compare
  • This version supports react-for-atom, but does break webpack.
  • Do not use this release with webpack.
  • No other changes.

v0.4.2

11 Aug 22:46
Compare
Choose a tag to compare

This release contains some bugfixes and changes of dependencies.

Bugfixes

  • Fix a bug with scrollToColumn being set out of range
  • fix a bug where calculated scrollbar face size is smaller #214 (thanks @u9520107!)

Deprecations

  • Remove usages of cloneWithProps in favor of React.cloneElement
  • Remove dependencies on ReactComponentWithPureRenderMixin, replaced with equivalent stub.

Other
Various typo fixes.

v0.4.1

09 Jul 17:03
Compare
Choose a tag to compare

Bugfixes:

  • Add back onRowDoubleClick to rows, accidentally lost in the syncing process. Thanks @difelice!

v0.4.0

07 Jul 21:28
Compare
Choose a tag to compare

Changelog:

Changes:

  • Adjusts the scrollbar to to not overlay the header or the footer. #138 mikestead
  • (NEW) Adds the onScrollStart property to Table, #147, @mikestead
  • Split styling and layout specific CSS. The table looks functionally the same, but things like backgrounds and colors can be styled using a the various style css files, or a larger theme file. Default theme will still apply. Thanks with help from @Andreyco
  • Include base (no-styling) with dist/fixed-data-table-base.css and add styling by editing or including dist/fixed-data-table-style.css
  • Column props now include headerClassName and footerClassName.

Bugfixes:

  • Force table height to be an integer, from PR 144, closes issue 80 (Thanks @gsklee)

Breaking changes:

  • If you have been using cellClassName to target the header or footer cells, you will need to now use the Column prop headerClassName or footerClassName, respectively.
  • If you have styled the table by specifying classnames that were not prepended by 'public,' (what we would consider 'private' classes), then the name of the component now has 'Layout' appended.

For example, if you styled .fixedDataTable_header, it is now .fixedDataTableLayout_header. In this case, you can still access it through its public classname, .public_fixedDataTable_header.

For styling, it is extremely important that you use the .public prepended classnames, as these will be more stable than the internal classes used purely for layout.

v0.3.0

12 Jun 18:42
Compare
Choose a tag to compare

Changes:

  • groupHeaderRenderer for FixedDataTableColumnGroup is now used for rendering group headers, as specified in documentation #151
  • Improved performance of layout calculation that had been major part of JS time spent for every prop update 9936c5b
  • Fixed rows positioning when using variable row heights #157
  • Added prop to allow rendering of a lot of columns without huge performance drop by paging the columns like we do for rows, add allowCellsRecycling={true} to column config to enable this per column #49
  • Changed cells to be rendered in absolute positions inside rows, to enable the above perf improvement.
  • Stopped supporting React 0.12.0, we upgraded our React API usage, mainly getDOMNode to findDOMNode.