Skip to content

Commit a35386a

Browse files
committed
docs(h-grid,toolbar): document toolbar grid prop deprecation
1 parent bc98090 commit a35386a

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

CHANGELOG.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ All notable changes for each version of this project will be documented in this
1010
- Added new property `toggleNodeOnClick` that determines whether clicking over a node will change its expanded state or not. Set to `false` by default.
1111
- `IgxPivotGrid`
1212
- `IPivotDimension` interface now exposes a property called `displayName` similar to the one in the `IPivotValue` interface. This property is optional and will be displayed inside the chips for rows and columns in the `IgxPivotGrid`. If the `displayName` property is not set, `memberName` will be used as a fallback.
13-
- `IgxHierarchicalGrid`
13+
- `IgxHierarchicalGrid`, `IgxGridToolbar`
1414
- The declaration of child layout toolbar templates no longer require explicit grid reference so the following:
1515
```html
1616
<igx-row-island>
@@ -21,6 +21,7 @@ All notable changes for each version of this project will be documented in this
2121
<igx-row-island>
2222
<igx-grid-toolbar *igxGridToolbar>
2323
```
24+
- With this change the `grid` property of the `IgxGridToolbar` has been deprecated as it's no longer needed and will be removed in a future version.
2425
- New directive - `igxIconButton` directive that provides a way to use an icon as a fully functional button has been added. The new `igxIconButton` comes in three types - flat, outlined and contained (default). All `igxButton`'s with type `icon` will be automatically migrated to the new `igxIconButton`'s with `ng update`.
2526
- `IgxButton`
2627
- **Behavioral Change** `buttonSelected` event is now emitted not only when a button gets selected, but also when it gets deselected. However, the event is no longer being emitted on initialization. If this event was used in a scenario where it is assumed that the button gets selected, it's a good idea the logic to be branched now based on `eventArgs.selected` condition.

0 commit comments

Comments
 (0)