- Support for ember 3.28+ by refactoring component file structure for converting to glimmer #345
- Removed polyfills no longer needed for supporting 3.28+
- Dropped support for Node 14.
- Removed yielded for head and foot from table api (Previously deprecated)
- cells no longer support the ability to specify
visibleon the cells themselves. Please setvisibleon the column - many booleans arguments if undefined are now treated as true instead of false (ex column.visible)
- Converted components to user glimmer syntax #345 #351
- Converted components to use template imports
- Updated husky/prettier/linters
- switch from npm to pnpm
- yield prop name in TBody/Row/Cell
- The column's
@filterFunctionnow gets an extra argument passed in with the row.
- import
deprecatefrom@ember/debuginstead of@ember/application/deprecations. This was causing runtime errors on ember 4.x.
- use
(has-block)helper fix erroring on ember v4
- relax
@ember/render-modifiersdependency to^1.0.2 || ^2.0.0
@loadDatafunction is invoked with acolumnFiltersparam which is an array of objects. Those objects now have apropproperty. This makes it easier to know which column you're filtering on, simplifying custom filtering logic. #296
- fix bug that made the
visibleColumnsto not update correctly under ember source >= 3.23
- update ember version and other dependencies
- update
deprecateusage - migrate travis to github actions
- fixes bug where the
@loadDatafunction could be running twice if a@pageNumberor@pageSizeargument was passed in to the component.
- new argument
@isColumnVisible. This argument can be used to initialize the column visibility in a programatic way. For example, let's say you store the initial column visibility in local storage, then you can use this function to initialize thevisiblecolumn of the specific column. The given function should return a boolean which will be assigned to thevisibleproperty of the column. An object representing the column is passed in. Sou can usecolumn.propandcolumn.nameto know which column your computed the visibility for.
- fix bug where the columns weren't unregistering
- run the
@registerApifunction in the actions queue to allow things like@registerApi={{fn (mut this.table)}}
- new argument
@registerApithat gets passed the public api of the table. With this object you can call actions to change the state of the table itself. Currently the same as the yieldedtable.actionsobject. - new action called
reloadData. Invoking this action will rerun the@loadDataargument to get fresh data.
- update ember version and other dependencies
role="button"was being applied to all<tr>elements, even if a click action was not provided.
- use ember on modifier on documentation and codebase
- use
this.when referencing properties on docs
- all components except
<YetiTable>are now private and no longer exposed to the application in the global namespace.
- added a new component
tbody. Unlike the current body component which yields a single record and iterates over the array for you,tbodyyields the array and you must iterate over the array yourself.
- the head and foot components have been deprecated and replaced with thead and tfoot
- added prettier to the project
- the yielded columns now have a
nameproperty. It defaults to the column's trimmedtextContentvalue, but it can be overrided by using a@name="your custom name"argument. This feature can be useful for "introspection" purposes, e.g if you want to show a list of the columns to the user.
- introduced new argument
@renderTableElement={{false}}. This prevents yeti table from automatically rendering the<table>element. When you set this argument asfalse, you are responsible for rendering the table element yourself using the yielded<t.table>component. This is a simple component that is now yielded that just renders the table element with the appropriate theme classes.
- updated internal dependencies
- migrate all components to be tagless (more in line with glimmer components)
- now you can use
@ignoreDataChanges={{true}}to prevent yeti from reacting to changes on the underlying data, resorting or refiltering. Useful when doing inline editing in a table. #151
- updated internal dependencies
- use
ember-on-modifier - use ember
fnhelper instead ofactionhelper
- allow usage of nested keys on the
@propargument. If the property is a nested property (one that contains periods), the table will not be updated when this nested property changes. This is due to@eachonly supporting one level of properties.
- updated dependencies
table.visibleRowsis no longer a number of visible rows but the rows data itself. If you want the number of visible rows, you can use{{table.visibleRows.length}}table.totalColumnswas renamed totable.columnsand is no longer a number of total columns but an array of objects that represent the columns. If you want the number of total columns, you can use{{table.columns.length}}table.visibleColumnsis no longer a number of visible columns but an array of objects that represent the visible columns. If you want the number of visible columns, you can use{{table.visibleColumns.length}}- the deprecated
@rowClassargument on<table.body>was removed. Use theme feature instead, e.g<YetiTable @theme={{hash tbodyRow="custom-row-class"}}>.
- now you can use
table.rows. This will contain an array of all the rows yeti table knows of. In the sync case, it will contain the entire dataset. In the async case, it will be the same astable.visibleRows. - now you can use
@visibleon any cell component. Useful if you need to escape the default@visiblevalue of the corresponding column e.g to always render pagination on the first row with a colspan
- updated dependencies and removed
@argumentdecorator because it was stopping us from supporting latest ember versions