You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+10-9Lines changed: 10 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,15 +21,16 @@ When working on an issue for the Ignite UI for Angular repository, you need to b
21
21
## Development - applicable to issues
22
22
23
23
### Statuses
24
-
1.`status: in-review` this is the initial status of an issue. If the label is not placed, go ahead and place it.
25
-
2.`status: in-development` this is the status once you start working on an issue. Assign the issue to yourself if it hasn't been assigned already and remove the previous status and assign it an in development status.
26
-
3.`status: by-design` this is the status of an issue that has been reviewed and has been determined that the current design of the feature is such that the issue describes the correct behavior as incorrect. Remove other statuses and place this status if you've reviewed the issue.
27
-
4.`status: third-party-issue` this is the status of an issue that has been reviewed, has been determined to be an issue, but the root case is not in the Ignite UI for Angular code. Example would be browser specific bugs caused by the particular browser's rendering or JavaScript engines, or an issue with the Angular framework. Remove other statuses and place only this one if you're the one performing the investigation.
28
-
5.`status: not-to-fix` this is the status of issues that derive from our code, but have been decided to leave as is. This is done when fixes require general design and/or architecture changes and are very risky.
29
-
6.`status: already-fixed` this status indicates that the issue is already fixed in the source code. When setting this status assign the person that logged the issue so that he can verify the issue is fixed in the respective development branch. Remove other statuses and place this status if you've reviewed the issue.
30
-
7.`status: cannot-reproduce` this status indicates that you cannot reproduce the issue in the source code. A reason may be because the issue is already fixed. When setting this status assign the person that logged the issue so that he can respond with more details on how to reproduce it.
31
-
8.`status: not a bug` this is the status of an issue that you reviewed and concluded that it's not a bug. You should comment explaining the reasons why you think the issue is not a bug.
32
-
9.`status: resolved` this is the status of an issue that has been fixed and there are active pull requests related to it.
24
+
1.`status: new` this is the initial status of an issue. This label is placed automatically.
25
+
2.`status: in-review` this is the status once someone picks up the issue and starts looking at it. Change the status to in-review when you pick it up.
26
+
3.`status: in-development` this is the status once you start working on an issue. Assign the issue to yourself if it hasn't been assigned already and remove the previous status and assign it an in development status.
27
+
4.`status: by-design` this is the status of an issue that has been reviewed and has been determined that the current design of the feature is such that the issue describes the correct behavior as incorrect. Remove other statuses and place this status if you've reviewed the issue.
28
+
5.`status: third-party-issue` this is the status of an issue that has been reviewed, has been determined to be an issue, but the root case is not in the Ignite UI for Angular code. Example would be browser specific bugs caused by the particular browser's rendering or JavaScript engines, or an issue with the Angular framework. Remove other statuses and place only this one if you're the one performing the investigation.
29
+
6.`status: not-to-fix` this is the status of issues that derive from our code, but have been decided to leave as is. This is done when fixes require general design and/or architecture changes and are very risky.
30
+
7.`status: already-fixed` this status indicates that the issue is already fixed in the source code. When setting this status assign the person that logged the issue so that he can verify the issue is fixed in the respective development branch. Remove other statuses and place this status if you've reviewed the issue.
31
+
8.`status: cannot-reproduce` this status indicates that you cannot reproduce the issue in the source code. A reason may be because the issue is already fixed. When setting this status assign the person that logged the issue so that he can respond with more details on how to reproduce it.
32
+
9.`status: not a bug` this is the status of an issue that you reviewed and concluded that it's not a bug. You should comment explaining the reasons why you think the issue is not a bug.
33
+
10.`status: resolved` this is the status of an issue that has been fixed and there are active pull requests related to it.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+36-5Lines changed: 36 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,12 +2,43 @@
2
2
3
3
All notable changes for each version of this project will be documented in this file.
4
4
5
+
## 15.1.0
6
+
7
+
### New Features
8
+
-`IgxColumnComponent`
9
+
- Added `currRec` and `groupRec` parameters to the `groupingComparer` function that give access to the all properties of the compared records.
10
+
11
+
### General
12
+
-`IgxPivotGrid`
13
+
- The `IgxPivotDateDimension` properties `inBaseDimension` and `inOption` have been deprecated and renamed to `baseDimension` and `options` respectively.
14
+
-`IgxGrid`
15
+
-**Breaking Change** The `onGroupingDone` output has been renamed to `groupingDone` to not violate the no on-prefixed outputs convention. Automatic migrations are available and will be applied on `ng update`.
16
+
-`DisplayDensity`
17
+
-**Breaking Change** The `onDensityChanged` output has been renamed to `densityChanged` to not violate the no on-prefixed outputs convention. All components exposing this event are affected. Automatic migrations are available and will be applied on `ng update`.
18
+
-`IgxGrid`, `IgxTreeGrid`, `IgxHierarchicalGrid`
19
+
-**Breaking Change** - `rowSelectionChanging` event arguments are changed. Now the `oldSelection`, `newSelection`, `added` and `removed` collections no longer consist of the row keys of the selected elements when the grid has set a primaryKey, but now in any case the row data is emitted.
20
+
When the grid is working with remote data and a primary key has been set- for the selected rows that are not currently part of the grid view, will be emitted a partial row data object.
21
+
-**Behavioral Change** - When selected row is deleted from the grid component `rowSelectionChanging` event will no longer be emitted.
22
+
-`IgxCarousel`
23
+
-**Breaking Change** The `onSlideChanged`, `onSlideAdded`, `onSlideRemoved`, `onCarouselPaused` and `onCarouselPlaying` outputs have been renamed to `slideChanged`, `slideAdded`, `slideRemoved`, `carouselPaused` and `carouselPlaying` to not violate the no on-prefixed outputs convention. Automatic migrations are available and will be applied on `ng update`.
24
+
-`IgxRadio`, `IgxRadioGroup`
25
+
- Added component validation along with styles for invalid state
26
+
-`IgxBadge`
27
+
- Added `shape` property that controls the shape of the badge and can be either `square` or `rounded`. The default shape of the badge is rounded.
28
+
-`IgxAvatar`
29
+
-**Breaking Change** The `roundShape` property has been deprecated and will be removed in a future version. Users can control the shape of the avatar by the newly added `shape` attribute that can be `square`, `rounded` or `circle`. The default shape of the avatar is `square`.
30
+
5
31
## 15.0.1
6
32
7
33
-`IgxGrid`
8
34
- Added new auto-sizing API `recalculateAutoSizes` that recalculates widths of columns that have size set to `auto`. Can be used in scenarios where you want to auto-size the columns again post initialization.
35
+
- Clicking with the Left Mouse key while holding `Ctrl` on selected cell will deselect the cell.
9
36
-`igxPivotGrid`
10
37
- Adding `aggregatorName` for pivot value configuration as an alternative to setting `aggregator` function. If both are set `aggregatorName` takes precedent. If none are set an error is thrown.
38
+
-`IgxSimpleCombo`
39
+
-**Behavioral Change**
40
+
- When the user clicks on the combo's input, the dropdown opens up.
41
+
- Keyboard navigation `ArrowUp` - when the combo is opened `ArrowUp` will close the dropdown if the search input is focused. If the active item is the first one in the list, the focus will be moved back to the search input while also selecting all of the text in the input. Otherwise `ArrowUp` will move to the previous list item.
11
42
12
43
## 15.0.0
13
44
@@ -90,7 +121,7 @@ All notable changes for each version of this project will be documented in this
90
121
91
122
### New Features
92
123
- The filtering logic inside the grid's Advanced Filtering is now extracted as a separate `IgxQueryBuilder` component. The Query Builder allows you to build complex queries by specifying AND/OR operators, conditions and values using the UI. It outputs an object describing the structure of the query. Use the `locale` property to modify the locale settings. The default value is resolved to the global Angular application locale. The `resourceStrings` allows changing the displayed strings.
93
-
124
+
94
125
- Code example below:
95
126
96
127
```html
@@ -126,7 +157,7 @@ All notable changes for each version of this project will be documented in this
126
157
<ng-template igxPivotValueChip let-value>
127
158
{{ value.member }}
128
159
</ng-template>
129
-
```
160
+
```
130
161
- Add support for usage with igxGridState to persist state of the pivotConfiguration with an additional `pivotConfiguration` option:
131
162
132
163
```html
@@ -142,7 +173,7 @@ All notable changes for each version of this project will be documented in this
142
173
```
143
174
144
175
One known issue of the igxGridState directive is that it cannot store functions as the state is stored as string.
145
-
As a result any custom functions set to `memberFunction`, `aggregator`, `formatter`, `styles` etc. will not be stored. Restoring any of these can be achieved with code on application level.
176
+
As a result any custom functions set to `memberFunction`, `aggregator`, `formatter`, `styles` etc. will not be stored. Restoring any of these can be achieved with code on application level.
146
177
Hence we have also exposed 2 new events:
147
178
- `dimensionInit` - emits when a dimension from the configuration is being initialized.
148
179
- `valueInit` - emits when a value from the configuration is being initialized.
@@ -202,7 +233,7 @@ All notable changes for each version of this project will be documented in this
202
233
<column width='auto' ...>
203
234
```
204
235
- Added support for restoring filtering expressions with custom filtering operands for the `IgxGridStateDirective`.
205
-
236
+
206
237
207
238
- Added the `IgcFormControl` directive that, when imported with its `IgcFormsModule`, is designed to seamlessly attach to form components from the Ignite UI for WebComponents package and allows using them in Angular templates and reactive forms with support for `ngModel` and `formControlName` directives. Currently the only Web Component with support through the directive is `igc-rating`.
208
239
@@ -217,7 +248,7 @@ All notable changes for each version of this project will be documented in this
217
248
218
249
## 14.0.0
219
250
220
-
- Added additional theme properties for the `IgxCalendar` so that it's easier to style the `:hover` and `:focus` states inside the selected date or range of dates.
251
+
- Added additional theme properties for the `IgxCalendar` so that it's easier to style the `:hover` and `:focus` states inside the selected date or range of dates.
221
252
- `IgxDatePicker` and `IgxDateRangePicker` now expose a `weekStart` input property like the `IgxCalendar`
222
253
- `IgxCombo` and `IgxSimpleComboComponent`
223
254
- The combobox `role`, `aria-haspopup`, `aria-expanded`, `aria-controls` and `aria-labelledby` attributes have been moved from combo wrapper to the combo input. Additionally the `IgxSimpleComboComponent` input is marked with `aria-readonly="false"` and `aria-autocomplete="list"` attributes. The `aria-labelled` attribute is applied to the combo dropdown as well and can be set by the `ariaLabelledBy` property, the combo label or placeholder. The serach input within the combo dropdown is now marked as `role="searchbox"`, `aria-label="search"` and `aria-autocomplete="list"`. The dropdown item container has `aria-activedescendant` attribute to identify the currently active element of the item list. The `IgxCombo` container is also marked as `aria-multiselectable="true"`. The dropdown header items role has been changed to `group`.
0 commit comments