|
2 | 2 |
|
3 | 3 | All notable changes for each version of this project will be documented in this file. |
4 | 4 |
|
| 5 | +## 20.0.0 |
| 6 | + |
| 7 | +### General |
| 8 | +- **Angular 20 Compatibility** - Ignite UI for Angular now plays nice with Angular 20! Upgrade your apps and enjoy the latest features. |
| 9 | +- `IgxActionStrip` |
| 10 | + - **Behavioral Changes** - When using the Action Strip standalone, outside of Grid, scenarios the component is no longer initially visible and the `hidden` property now defaults to `true`. |
| 11 | +- `IgxChip` |
| 12 | + - **Behavioral Change** The `variant` is now strictly typed with the union of supported options and no longer accepts invalid values for the default state, provide no value (nullish) instead is needed. |
| 13 | + |
| 14 | +### New Features |
| 15 | +- `IgxGrid`, `IgxTreeGrid`, `IgxHierarchicalGrid`, `IgxPivotGrid` |
| 16 | + - Added a new `igxGridEmpty` template directive that allows assigning the `emptyGridTemplate` declaratively, without the need to get and assign reference, like other grid templates like: |
| 17 | + ```html |
| 18 | + <igx-grid> |
| 19 | + <ng-template igxGridEmpty> |
| 20 | + <!-- content to show when the grid is empty --> |
| 21 | + </ng-template> |
| 22 | + </igx-grid> |
| 23 | + ``` |
| 24 | + - Added a new `igxGridLoading` template directive that allows assigning the `loadingGridTemplate` declaratively, without the need to get and assign reference, like other grid templates like: |
| 25 | + ```html |
| 26 | + <igx-grid> |
| 27 | + <ng-template igxGridLoading> |
| 28 | + <!-- content to show when the grid is loading --> |
| 29 | + </ng-template> |
| 30 | + </igx-grid> |
| 31 | + ``` |
| 32 | + |
| 33 | +## 19.2.0 |
| 34 | + |
| 35 | +### General |
| 36 | +- `IgxCarousel` |
| 37 | + - Removed deprecated property `keyboardSupport`. |
| 38 | +- `IgxSlide` |
| 39 | + - **Deprecation** - `tabIndex` has been deprecated and will be removed in a future version. |
| 40 | +- `IgxGrid`, `IgxHierarchicalGrid`, `IgxTreeGrid` |
| 41 | + - A column's `minWidth` and `maxWidth` constrain the user-specified `width` so that it cannot go outside their bounds. |
| 42 | + - In SSR mode grid with height 100% or with no height will render on the server with % size and with no data. The grid will show either the empty grid template or the loading indicator (if isLoading is true). |
| 43 | + - In SSR mode grid with width 100% or with no width will render on the server with % size and with all columns. |
| 44 | + - The `pagingMode` property can now be set as simple strings `'local'` and `'remote'` and does not require importing the `GridPagingMode` enum. |
| 45 | +- `IgxHierarchicalGrid` |
| 46 | + - Introduced a new advanced filtering capability that enables top-level records to be dynamically refined based on the attributes or data of their associated child records. |
| 47 | + - Added a new `schema` input property that can be used to pass collection of `EntityType` objects. This property is required for remote data scenarios. |
| 48 | +- `IgxQueryBuilderComponent`, `IgxAdvancedFilteringDialogComponent` |
| 49 | + - Added support for entities with hierarchical structure. |
| 50 | +- `EntityType` |
| 51 | + - A new optional property called `childEntities` has been introduced that can be used to create nested entities. |
| 52 | + |
| 53 | +## 19.1.1 |
| 54 | +### New Features |
| 55 | +- IgxListItem |
| 56 | + - Added a new `selected` input property, making it easier to indicate when a list item is selected by applying styling responsible for that state. |
| 57 | + |
5 | 58 | ## 19.1.0 |
6 | 59 | ### General |
7 | 60 | - `IgxCarousel` |
8 | 61 | - **Behavioral Changes** - the `maximumIndicatorsCount` input property now defaults to `10`. |
9 | 62 | - **Deprecation** - `CarouselIndicatorsOrientation` enum members `top` and `bottom` have been deprecated and will be removed in a future version. Use `start` and `end` instead. |
10 | 63 |
|
| 64 | +### New Features |
| 65 | +- `IgxBanner` |
| 66 | + - Introduced a new `expanded` input property, enabling dynamic control over the banner's state. The banner can now be programmatically set to expanded (visible) or collapsed (hidden) both initially and at runtime. Animations will trigger during runtime updates — the **open animation** plays when `expanded` is set to `true`, and the **close animation** plays when set to `false`. However, no animations will trigger when the property is set initially. |
| 67 | + - The banner's event lifecycle (`opening`, `opened`, `closing`, `closed`) only triggers through **user interactions** (e.g., clicking to open/close). Programmatic updates using the `expanded` property will not fire any events. |
| 68 | + - If the `expanded` property changes during an ongoing animation, the current animation will **stop** and the opposite animation will begin from the **point where the previous animation left off**. For instance, if the open animation (10 seconds) is interrupted at 6 seconds and `expanded` is set to `false`, the close animation (5 seconds) will start from its 3rd second. |
| 69 | +- `IgxQueryBuilder` has a new design that comes with an updated appearance and new functionality |
| 70 | + - `IgxQueryBuilderComponent` |
| 71 | + - Introduced the ability to create nested queries by specifying IN/NOT IN operators. |
| 72 | + - Introduced the ability to reposition condition chips by dragging or using `Arrow Up/Down`. |
| 73 | + - Added the `entities` property that accepts an array of `EntityType` objects describing an entity with its name and an array of fields. The `fields` input property has been deprecated and will be removed in a future version. Automatic migrations are available and will be applied on `ng update`. |
| 74 | + - Added `disableEntityChange` property that can be used to disable the entity select on root level after the initial selection. Defaults to `false`. |
| 75 | + - Added `disableReturnFieldsChange` property that can be used to disable the fields combo on root level. Defaults to `false`. |
| 76 | + - Added the `canCommit`, `commit` and `discard` public methods that allows the user to save/discard the current state of the expression tree. |
| 77 | + - Added option to template the search value input: |
| 78 | + ``` |
| 79 | + <ng-template igxQueryBuilderSearchValue |
| 80 | + let-searchValue |
| 81 | + let-selectedField = "selectedField" |
| 82 | + let-selectedCondition = "selectedCondition" |
| 83 | + let-defaultSearchValueTemplate = "defaultSearchValueTemplate"> |
| 84 | + @if (selectedField?.field === 'Id' && selectedCondition === 'equals'){ |
| 85 | + <input type="text" required [(ngModel)]="searchValue.value"/> |
| 86 | + } @else { |
| 87 | + <ng-container #defaultTemplate *ngTemplateOutlet="defaultSearchValueTemplate"></ ng-container> |
| 88 | + } |
| 89 | + </ng-template> |
| 90 | + ``` |
| 91 | + - **Behavioral Changes** |
| 92 | + - Expression enters edit mode on single click, `Enter` or `Space`. |
| 93 | + - Selecting conditions inside the `IgxQueryBuilderComponent` is no longer supported. Grouping/ungrouping expressions is now achieved via the newly exposed Drag & Drop functionality. |
| 94 | + - Deleting multiple expressions through the context menu is no longer supported. |
| 95 | + - `IgxQueryBuilderHeaderComponent` |
| 96 | + - **Behavioral Change** |
| 97 | + - Legend is no longer shown. |
| 98 | + - If the `title` input property is not set, by default it would be empty string. |
| 99 | + - **Deprecation** |
| 100 | + - The `showLegend` and `resourceStrings` input properties have been deprecated and will be removed in a future version. Automatic migrations are available and will be applied on `ng update`. |
| 101 | +- `IFilteringExpression` |
| 102 | + - A new optional property called `conditionName` has been introduced. This would generally be equal to the existing `condition.name`. |
| 103 | +- `IFilteringOperation` |
| 104 | + - A new optional property called `isNestedQuery` has been introduced. It's used to indicate whether the condition leads to a nested query creation. |
| 105 | + |
11 | 106 | ## 19.0.0 |
12 | 107 | ### General |
13 | 108 | - `IgxFilteringService`, `IgxGridBaseDirective` |
@@ -77,6 +172,7 @@ All notable changes for each version of this project will be documented in this |
77 | 172 | - `IgxGridState` |
78 | 173 | - When possible the state directive nows reuses the column that already exists on the grid when restoring the state, instead of creating new column instances every time. This removes the need to set any complex objects manually back on the column on `columnInit`. The only instance where this is still necessary is when the column (or its children in case of column groups) have no `field` property so there's no way to uniquely identify the matching column. |
79 | 174 | - Added support for persisting Multi-Row Layout. |
| 175 | + |
80 | 176 | ### Themes |
81 | 177 | - **Breaking Change** `Palettes` |
82 | 178 | - All palette colors have been migrated to the [CSS relative colors syntax](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_colors/Relative_colors). This means that color consumed as CSS variables no longer need to be wrapped in an `hsl` function. |
|
0 commit comments