Table 5.0 changes

Cell format "v2" components

To prepare for the Popover changes coming in Blueprint v5.0, we're providing "v2" variants of @blueprintjs/table components which use Popover2 instead of Popover. Migrate to these now in order to ensure a smooth migration path.

These components are available in @blueprintjs/table v4.x:

JSONFormat2

Replacement for JSONFormat, with notable changes (these also apply to TruncatedFormat2):

• There is no more .bp4-popover-wrapper element. If you use custom styling on top of the default Blueprint Cell and/or JSONFormat component styles, you may need to visually test your DOM layout inside the cell to make sure the removal of this element does not break styling (but this is very unlikely).

That's it. The props interface is the same as JSONFormat.

TruncatedFormat2

Replacement for TruncatedFormat, with the same notable changes changes as JSONFormat2.

Other changes

You may be wondering about other "v2" components in @blueprintjs/table. Some of these will continue to be available in Blueprint v5 (no migration required), while others will be automatically upgraded (we expect no breaking changes).

ColumnHeaderCell2, RowHeaderCell2

These components use Popover2 (via ContextMenu2) instead of Popover. They have no API changes from their "v1" counterparts, and we don't expect any breaking changes as a result of the Popover -> Popover2 migration. They are provided as a convenience in Blueprint v4 for custom row/cell header renderers, but if you don't choose to use them, they will be automatically and transparently upgraded in v5 with no action required.

Table2

<Table2> is available in Blueprint v4 as a replacement for <Table>, but the latter API is not being removed in Blueprint v5 (due to a reduced scoping of v5.0 breaking changes). So you don't necessarily need to migrate their usage just yet. Those breaking changes are coming in @blueprintjs/table v6.0, along with the removal of deprecated hotkeys APIs.