Releases: CrowdStrike/ember-headless-table
[email protected]
Patch Changes
- #236
3a737e9
Thanks @NullVoxPopuli! - Use more permissive peer ranges for@ember/test-helpers
,@ember/test-waiters
, andember-source
.
[email protected]
[email protected]
Patch Changes
-
#226
6c58dfd
Thanks @nicolechung! - Bugfix: the plugin for resize was not checking if the table was destroyed first.This fixes that so the observer is not listening for a removed table, which was causing an error in the preferences (since it was trying to set preferences for a table which is not on screen)
[email protected]
[email protected]
[email protected]
Major Changes
-
#176
f3435c3
Thanks @NullVoxPopuli! - In prepr for supporting Glint 1.0,
ember-headless-table no longer will support TypeScript < 4.8.Additionally, the support policy is changing from a minimum version, to a rolling window policy, as described in https://semver-ts.org.
The current and prior two TypeScript versions will be supported, giving a rolling window of 3 TypeScript versions.
Patch Changes
[email protected]
Patch Changes
- #157
57091d0
Thanks @nicolechung! - Added toStyle helper in column-resizing plugin > helper. This should fix when aminWidth
is passed in the column config and not getting converted tomin-width
for the style attribute string.
[email protected]
Patch Changes
-
#148
9b9fbe1
Thanks @NullVoxPopuli! - Support [email protected]. Test ember-source@v5 to the allowed peer versions for headless-table -
#149
8b8f170
Thanks @nicolechung! - Bugfix, change minWidth to min-width for the Sticky columns plugin
[email protected]
Patch Changes
-
#118
c02d49d
Thanks @NullVoxPopuli! - Address an issue where instances of plugins would be held on to after a Table is destroyed.This caused a memory leak due how plugins, and their associated metadata, held on to
Table instances, which in turn, held on to the owner / container.This was caused by the utility methods in
ember-headless-table/plugins
,preferences
meta
options
Because data was stored in (Weak)Maps in module-space.
This alone isn't a problem, but they were never cleaned up when the table was destroyed.Cleanup of these objects could have occured via
associateDestroyableChild
andregisterDestructor
from@ember/destroyable
, but it was easier to instead have this happen automatically via hosting the
data needed for the "plugins utils" on the table itself. Since each plugin util requires "some instance of something",
be that a row, column, or table, there is a direct path to the table, and therefor a direct way to access
memory-scoped (Weak)Maps.
[email protected]
Patch Changes
- #123
972749b
Thanks @NullVoxPopuli! - Fix an issue where columns using the ColumnResize plugin with the option isResizing set to false, the plugin could not recognize the column as having resizing turned off"