All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
- Nothing currently.
- Fixed example how to use
ColumnDefinition::merge()
in the docs. - Bugfix issue #33: With active filters the array grid source type page count still is calculated based on all grid records, not the filtered grid entries, resulting in added blank pages at the end.
- No removals.
- New event to customize column definitions conditionally:
'hyva_grid_column_definition_build_after_' . $gridNameSuffix
Thanks to @paugnu for the PR!
- No changes
- No removals.
- Filters now can have source models:
<filter column="store_id" source="\Magento\Config\Model\Config\Source\Store"/>
- No changes
- No removals.
- Support collections that use the generic entity type
\Magento\Framework\View\Element\UiComponent\DataProvider\Document
This is mainly used in the standard adminhtml (non-hyva) grids. For example `Magento\Sales\Model\ResourceModel\Order\Grid\Collection´
- Backward compatible bugfix for select filter with ajax pagination.
- No removals.
- Add feature to declare default search criteria bindings for embedded grids. More information can be found in the docs.
- A number of small bugfixes that I forgot to include individually in this changelog. Still getting used to it.
- No removals.
- Add this CHANGELOG.md file.
- New column attribute
initiallyHidden
. When set totrue
, a column will be rendered in HTML but hidden by JavaScript on the initial page load. The Display dropdown can be used to show the column when needed. Thanks to @paugnu for this feature. - Buttons to navigate to the first and last page are now part of the pagination. Thanks to @Bartlomiejsz for this feature.
- New
pager
attributeenabled
. When set tofalse
no pagination is rendered, and no current page and page size is set on the search criteria passed to the grid data providers. - Ajax Paging. Ajax paging is the default navigation mode. It can be disabled by setting the
useAjax
attribute on thepager
element tofalse
.<pager useAjax="false"/>
.
- Changed the column type
long_text
to function as a non-truncating text type. The default behavior remains that text content is truncated if it's longer than 30 characters.
- No removals.