Skip to content

Latest commit

 

History

History
770 lines (552 loc) · 36.9 KB

File metadata and controls

770 lines (552 loc) · 36.9 KB

Changelog

Release (2026-02-05)

  • @universal-ember/table 3.6.2 (patch)

🐛 Bug Fix

Committers: 1

Release (2026-02-04)

@universal-ember/table 3.6.1 (patch)

🐛 Bug Fix

  • @universal-ember/table, test-app
    • #161 fix: addMissingColumnsToMap skips new columns when stale keys exist in saved order (@johanrd)

📝 Documentation

  • docs-app

Committers: 1

Release (2026-01-28)

@universal-ember/table 3.6.0 (minor)

🚀 Enhancement

  • @universal-ember/table, test-app
    • #156 Add reactive thunk overload to preferences config option (@johanrd)

📝 Documentation

  • docs-app
    • #155 fix(docs): Upgrade @html-next/vertical-collection as an attempt to solve #61 (@johanrd)
  • docs-api, docs-app
    • #154 fix(docs): Add discoverable cross linking between • Github • API Reference • Docs app (@johanrd)

Committers: 1

Release (2026-01-28)

@universal-ember/table 3.5.0 (minor)

🚀 Enhancement

  • @universal-ember/table, test-app
    • #150 Fix/column reordering reactive preferences (@johanrd)

🐛 Bug Fix

  • @universal-ember/table, test-app
    • #150 Fix/column reordering reactive preferences (@johanrd)
    • #149 fix(preferences): make restore() reactive by using TrackedMap (@johanrd)

Committers: 1

Release (2026-01-26)

@universal-ember/table 3.4.3 (patch)

🐛 Bug Fix

  • @universal-ember/table
    • #148 remove the v1 addon ember-tracked-storage-polyfill as dep (@johanrd)

🏠 Internal

Committers: 2

Release (2025-12-04)

@universal-ember/table 3.4.2 (patch)

🐛 Bug Fix

  • @universal-ember/table
    • #136 Fix ColumnResizing preferences not restoring saved widths (@johanrd)

Committers: 1

Release (2025-12-03)

@universal-ember/table 3.4.1 (patch)

🐛 Bug Fix

  • @universal-ember/table
    • #131 fix: mark touchstart listener as passive in resize handle (@johanrd)

📝 Documentation

Committers: 2

Release (2025-11-11)

@universal-ember/table 3.4.0 (minor)

🚀 Enhancement

  • docs-app, @universal-ember/table, test-app
    • #125 add isResizable helper (@johanrd)
    • #124 feat(column-reordering): add orderedColumnsFor helper + fix two skipped tests (@johanrd)

🐛 Bug Fix

  • @universal-ember/table, test-app

Committers: 1

Release (2025-11-06)

@universal-ember/table 3.3.0 (minor)

🚀 Enhancement

  • @universal-ember/table
    • #122 Prevent auto-redistributing with tableLayout: 'fixed' (@johanrd)
  • docs-app, @universal-ember/table, test-app
    • #120 Add table-level defaultCellValue config option (@johanrd)

🐛 Bug Fix

  • @universal-ember/table
    • #121 Fixes infinite resize loop at non-100% zoom levels caused by subpixel rounding errors. (@johanrd)

📝 Documentation

🏠 Internal

Committers: 3

Release (2025-10-03)

@universal-ember/table 3.2.0 (minor)

🚀 Enhancement

  • docs-app, @universal-ember/table, test-app

🐛 Bug Fix

  • docs-app, @universal-ember/table, test-app

📝 Documentation

Committers: 3

Release (2025-08-25)

@universal-ember/table 3.1.1 (patch)

🐛 Bug Fix

  • @universal-ember/table
    • #99 Pass through generics to ComponentLike<CellContext<T>> (@johanrd)

Committers: 1

Release (2025-08-25)

@universal-ember/table 3.1.0 (minor)

🚀 Enhancement

  • docs-app, @universal-ember/table, test-app
    • #97 Simple column resizing setting with tableLayout: 'fixed' (@johanrd)

Committers: 1

Release (2025-08-25)

@universal-ember/table 3.0.4 (patch)

🐛 Bug Fix

  • @universal-ember/table, test-app
    • #95 Make sure generics are passed into helpers (@johanrd)

📝 Documentation

  • docs-app
    • #68 double FPS in "Lots of data (no virtualization)" when utilising key in #each (@johanrd)

Committers: 1

Release (2025-03-27)

@universal-ember/table 3.0.3 (patch)

🐛 Bug Fix

Committers: 1

Release (2025-03-27)

@universal-ember/table 3.0.2 (patch)

🐛 Bug Fix

  • docs-app, @universal-ember/table, test-app

📝 Documentation

Committers: 1

Release (2025-03-27)

@universal-ember/table 3.0.1 (patch)

🐛 Bug Fix

📝 Documentation

Committers: 2

Release (2025-03-23)

@universal-ember/table 3.0.0 (major)

💥 Breaking Change

  • Other
  • docs-app, @universal-ember/table, test-app
    • #15 Remove support for @types/ember*, now only supporting the official types from ember-source (@NullVoxPopuli)

🚀 Enhancement

  • docs-app, @universal-ember/table, test-app
  • docs-api, docs-app, @universal-ember/table, test-app

🐛 Bug Fix

📝 Documentation

  • docs-api, docs-app, test-app
    • #32 Use Vite (docs, tests) / Rewrite the docs / document things in terms of gjs and gts (@NullVoxPopuli)

🏠 Internal

Committers: 1

2.1.4

Patch Changes

  • #236 3a737e9 Thanks @NullVoxPopuli! - Use more permissive peer ranges for @ember/test-helpers, @ember/test-waiters, and ember-source.

2.1.3

Patch Changes

  • #233 4dbf668 Thanks @joelamb! - Fixes column resize and preference save sequencing to ensure that the functions always run in the correct order.

2.1.2

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)

2.1.1

Patch Changes

  • #219 4172870 Thanks @joelamb! - Column widths are saved and reset in a single call to the preferences service, rather than on a per column basis, for improved UI performance

2.1.0

Minor Changes

  • #211 0a9415c Thanks @joelamb! - Persists resized column widths to preferences. Width values are saved as strings after resizing. If present in preferences, width value will be restored to the table, overriding any initial options passed in.

Patch Changes

  • #214 58b2866 Thanks @joelamb! - Refactor to bulk reset column visibility preferences in a single call to the preferences service

2.0.0

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

1.4.5

Patch Changes

  • #157 57091d0 Thanks @nicolechung! - Added toStyle helper in column-resizing plugin > helper. This should fix when a minWidth is passed in the column config and not getting converted to min-width for the style attribute string.

1.4.4

Patch Changes

1.4.3

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 and registerDestructor 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.

1.4.2

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"

1.4.1

Patch Changes

  • #121 2175782 Thanks @NullVoxPopuli! - Add new util for the resizing plugin to help styles cells in non-header rows in non-tables (such as grids).

    To use it,

    import { styleStringFor } from "ember-headless-table/plugins/column-resizing";
    
    // ...
    
    // rows.gjs
    <template>
      {{#each @table.rows as |row|}}
        <div role="row">
          {{#each @table.columns as |column|}}
            <div
              role="cell"
              style={{styleStringFor column}}
            >{{column.getValueForRow row}}</div>
          {{/each}}
        </div>
      {{/each}}
    </template>

1.4.0

Minor Changes

  • #110 a9c19c7 Thanks @NullVoxPopuli! - Add new "query" util: hasPlugin, allowing consumers of the headlessTable to ask if a plugin is active and get a boolean response.

    Example:

    import { headlessTable } from "ember-headless-table";
    import { hasPlugin } from "ember-headless-table/plugins";
    import { DataSorting } from "ember-headless-table/plugins/data-sorting";
    
    // ... ✂️ ...
    let table = headlessTable(this, {
      columns: () => [],
      data: () => [],
      plugins: [DataSorting],
    });
    
    hasPlugin(table, DataSorting); // => true

Patch Changes

  • #108 40649c9 Thanks @NullVoxPopuli! - deserializeSorts now will gracefully return an empty array upon receiving empty input.

    Example:

    import { deserializeSorts } from "ember-headless-table";
    
    deserializeSorts(""); // => []

    Previously, an error would be reported:

    No key found for input: `` using `.` as a separator
    

    which wasn't all that helpful.

    When using the data-sorting plugin with this util, it is perfectly safe to "deserialize sorts" to an empty array and have that empty array be equivelant to no sorting being applied at all.

1.3.0

Minor Changes

  • #94 310a6e0 Thanks @NullVoxPopuli! - An alternative, yet more verbose, option is now available for the sticky / pinnable columns plugin.

    This is, in part, due to waiting on RFC#883: add new timing capabilities to modifier manager.

    But also, as an escape hatch for performance sensitive situations where one would want to avoid altering any style attributes during render (as is one of the primary use cases of RFC#883) as this causes repaint calculations and degraded performance in the browser.

    This new technique for the sticky/pinnable colums plugin allows you to set the style attribute so that the browser can calculate layout in a single pass.

    To opt in to this, two things must be done:

    1. invoke the styleStringFor helper in the template, and set the result to the style attribute for the th and td cells.

      import { styleStringFor } from "ember-headless-table/plugins/sticky-columns";
      
      // ...
      
      <template>
        <div class="h-full overflow-auto">
          <table>
            <thead>
              <tr class="relative">
                {{#each @table.columns as |column|}}
                  <th style="{{styleStringFor column}}">
                    {{column.name}}
                  </th>
                {{/each}}
              </tr>
            </thead>
            <tbody>
              {{#each @table.rows as |row|}}
                <tr class="relative">
                  {{#each @table.columns as |column|}}
                    <td style="{{styleStringFor column}}">
                      {{column.getValueForRow row}}
                    </td>
                  {{/each}}
                </tr>
              {{/each}}
            </tbody>
          </table>
        </div>
      </template>
    2. when configuring the StickyColumns plugin in headlessTable, configure the the workaroundForModifierTimingUpdateRFC883 flag to true. This allows td and th cells to have modifiers without causing repaints due to style changes caused by the sticky columns plugin.

    class Example {
      table = headlessTable(this, {
        columns: () => [
          // ...
        ],
        // ...
        plugins: [
          StickyColumns.with(() => ({
            workaroundForModifierTimingUpdateRFC883: true,
          })),
        ],
      });
    }

Patch Changes

  • #81 57c22d4 Thanks @NullVoxPopuli! - Prevent hard-to-debug issues that occur with incorrect column configs. One such way problems can occur is when the key property is duplicated for multiple column configs.

    This is now eagerly prevented via dev-time Error. All the column config validity checking code is removed in production builds via @embroider/macros macroCondition(isDevelopingApp()).

1.2.0

Minor Changes

  • #58 f885ebb Thanks @NullVoxPopuli! - New Metadata plugin, for allowing arbitrary data to be stored for each column as well as the whole table. This can be useful eliminating prop-drilling in a UI Table implementation consuming the headlessTable.

    For example, setting up the table can be done like:

    import { headlessTable } from "ember-headless-table";
    
    class Example {
      /* ... */
    
      table = headlessTable(this, {
        columns: () => [
          { name: "A", key: "A" },
          {
            name: "B",
            key: "B",
            pluginOptions: [
              Metadata.forColumn(() => ({
                isBulkSelectable: false,
              })),
            ],
          },
          {
            name: "D",
            key: "D",
            pluginOptions: [Metadata.forColumn(() => ({ isRad: this.dRed }))],
          },
        ],
        data: () => DATA,
        plugins: [
          Metadata.with(() => ({
            onBulkSelectionChange: (...args) => this.doSomething(...args),
          })),
        ],
      });
    }

    To allow "bulk selection" behaviors to be integrated into how the Table is rendered -- which for fancier tables, my span multiple components.

    For example: rows may be their own component

    // Two helpers are provided for accessing your Metadata
    import {
      forColumn /*, forTable */,
    } from "ember-headless-table/plugins/metadata";
    
    const isBulkSelectable = (column) => forColumn(column, "isBulkSelectable");
    
    export const Row = <template>
      <tr>
        {{#each @table.columns as |column|}}
          {{#if (isBulkSelectable column)}}
    
            ... render some checkbox UI ...
    
          {{else}}
            <td>
              {{column.getValueForRow @datum}}
            </td>
          {{/if}}
        {{/each}}
      </tr>
    </template>;
  • #66 3075a5c Thanks @NullVoxPopuli! - Add a new API for the column-reordering plugin that allows for managing column order independently of the table's column order, for example, in a configuration UI / preview, one may want to see how their changes will look before applying them to the table.

    To use this new API, there are two relevant imports:

    import {
      ColumnOrder,
      setColumnOrder,
    } from "ember-headless-table/plugins/column-reordering";

    To manage the "preview column order", you'll want to instantiate the ColumnOrder class, and then once your changes are done, call setColumnOrder and pass both the table and the ColumnOrder instance:

    class Demo {
      @tracked pendingColumnOrder;
    
      changeColumnOrder = () => {
        this.pendingColumnOrder = new ColumnOrder({
          columns: () => this.columns,
        });
      };
    
      handleReconfigure = () => {
        setColumnOrder(this.table, this.pendingColumnOrder);
        this.pendingColumnOrder = null;
      };
    }

    In this example, when working with this.pendingColumnOrder, you may use familiar "moveLeft" and "moveRight" behaviors,

    {{#let this.pendingColumnOrder as |order|}}
    
      {{#each order.orderedColumns as |column|}}
    
        <button {{on "click" (fn order.moveLeft column.key)}}> ⇦ </button>
    
        {{column.name}}
    
        <button {{on "click" (fn order.moveRight column.key)}}> ⇨ </button>
    
      {{/each}}
    
      <button {{on "click" this.handleReconfigure}}>Submit changes</button>
    {{/let}}

Patch Changes

  • #63 ecb68ff Thanks @NullVoxPopuli! - Previously, ember-headless-table's releases were managed by semantic-release. Now, they are managed by changesets, which is a bit more manual, but has far better monorepo support and allows catering to humans when it comes to changelogs.

  • #61 0356997 Thanks @NullVoxPopuli! - Fixes the issue reported in CrowdStrike/ember-headless-table#60 Where the column reordering and visibility plugins were not integrating well together. In short, moving column, then hiding that same column, then moving a column "over the gap" between the columns resulted in all column reordering no longer working. Using both of the plugins together should now work as intuitively expected.

Features

  • plugin, resizing: add helper for knowing if a column has a resize handle (f525f50)

1.0.1 (2022-11-06)

Bug Fixes

  • deps: update dependency highlightjs-glimmer to v2 (0881e12)

1.0.0 (2022-11-02)

Bug Fixes

  • column-reordering: reordering reactivity restored (bf8153c)
  • columnReordering: rework how order state is maintained (39ae71e)
  • columnResizing: fix the resize-handle modifier (e17c232)
  • columnResizing: resizeHandle modifier needs to be an ember-modifier (90f7577)
  • columnVisibility: bug where default hidden could not be unhidden (e6b7239)
  • columnVisibility: work around a bug with tracked-built-ins' delete not being reactive (ce62498)
  • columnVisibilty: bug where default / preferences clearing calculation was incorrect (e3e8480)
  • deps: update dependency @ember/test-waiters to ^3.0.2 (dcb45d1)
  • resizing: resizing depends on column order, not just visibility (6ac95ef)

Features

  • columnReordering: preferences are now persisted and read from (96e13c1)
  • initial implementation (0fc2cbc)
  • plugin: implement row selection plugin (e46ce50)
  • plugins: simplify working with columns among plugins (48ef0bb)
  • plugin: sticky columns (b9b8bfa)
  • table: support @use (6561c30)

BREAKING CHANGES

  • brand new addon
  • copied code from internal project
  • successful build

This is an incremental step, as there is some dev work yet to complete

  • finish plugins work
  • rename @crowdstrike/ember-headless-table to ember-headless-table
  • Button up C.I.
  • Create docs site with lots of examples, how to write plugins, etc