.github/ISSUE_TEMPLATE/question.md

@@ -9,7 +9,4 @@ projects: IgniteUI/16
 ---
 
 ## Question  
-I have an issue with "x" and I'm not sure if I'm doing it right.
-
- * igniteui-angular version: 
- * browser: 
+For questions, please use the `Discussions` tab of the repository!

.vscode/launch.json

@@ -19,21 +19,51 @@
             }
         },
         {
-            "name": "Run migration",
+            "name": "Run migrations",
             "request": "launch",
             "type": "node",
-            "cwd": "<directory to apply migrations in>",
+
+            // "cwd": "<absolute directory of the project, having an old version of igniteui-angular, on which the migrations are applied>",
+            "cwd": "C:\\Users\\User\\Desktop\\ng_proj\\test_migrations",
             "args": [
                 "-r",
+
+                // you need to install ts-node for the test project
                 "ts-node/register",
-                // e.g. "${env:AppData}/npm/node_modules/@angular/cli/bin/ng"
-                "<path/to/ng>", "g",
-                "<../path/to>/igniteui-angular/projects/igniteui-angular/migrations/migration-collection.json:migration-<number>"
+
+                // "<path/to/ng>", "g",
+                "${env:AppData}/npm/node_modules/@angular/cli/bin/ng", "g",
+
+                // "<../../relative/path/from/cwd/to>/igniteui-angular/projects/igniteui-angular/migrations/migration-collection.json:migration-<number>
+                "../../../../../work/git/igniteui-angular/projects/igniteui-angular/migrations/migration-collection.json:migration-24"
             ],
             "env": {
                 "TS_NODE_PROJECT": "${workspaceFolder}/projects/igniteui-angular/migrations/tsconfig.json"
             }
         },
+        {
+            "name": "Run schematics",
+            "request": "launch",
+            "type": "node",
+
+            // "cwd": "<absolute directory of the project, created with ng cli, on which the 'ng add' schematic is applied>"
+            "cwd": "C:\\Users\\User\\Desktop\\ng_proj\\test_schematics",
+            "args": [
+                "-r",
+
+                // you need to install ts-node for the test project
+                "ts-node/register",
+
+                // "<path/to/ng>", "g",
+                "${env:AppData}/npm/node_modules/@angular/cli/bin/ng", "g",
+
+                // "<../../relative/path/from/cwd/to>/igniteui-angular/projects/igniteui-angular/schematics/collection.json:ng-add"
+                "../../../../../work/git/igniteui-angular/projects/igniteui-angular/schematics/collection.json:ng-add"
+            ],
+            "env": {
+                "TS_NODE_PROJECT": "${workspaceFolder}/projects/igniteui-angular/schematics/tsconfig.json"
+            }
+        },
         {
             "name": "Typedoc plugin",
             "type": "node",

CHANGELOG.md

@@ -2,8 +2,121 @@
 
 All notable changes for each version of this project will be documented in this file.
 
+## 14.1.0
+
+### New Features
+- `IgxCombo` and  `IgxSimpleComboComponent`
+    - `filterFunction` input is added. The new property allows changing of the way filtering is done in the combos. By default filtering is made over the values in combo's data when it is a collection of primitive values, or over the values as defined in `displayKey` of the combo. If custom filtering function is provided filtering will be done as specified in the provided function.
+    - `filteringOptions` are extended and now contains `filterable` and `filteringKey` properties. Setting `filterable` determines whether combo will be filterable. By default filtering is done over the data value when they are primitive, or over the field of the values equal to `displayKey`. `filteringKey` allows to filter data by any data related key.
+
+- `igxPivotGrid`
+    - Add option to template the pivot value chip content:
+    ```
+    <ng-template igxPivotValueChip let-value>
+            {{ value.member }}
+    </ng-template>
+    ``` 
+    - Add support for usage with igxGridState to persist state of the pivotConfiguration with an additional `pivotConfiguration` option:
+
+    ```html
+     <igx-pivot-grid
+            #grid1
+            [igxGridState]="options" ...
+    ```
+
+    ```
+        public options : IGridStateOptions = {
+        pivotConfiguration: true
+    };
+    ```
+
+    One known issue of the igxGridState directive is that it cannot store functions as the state is stored as string.
+    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. 
+    Hence we have also exposed 2 new events:
+        - `dimensionInit` - emits when a dimension from the configuration is being initialized.
+        - `valueInit` - emits when a value from the configuration is being initialized.
+    Which can be used to set back any custom functions you have in the configuration.
+    The default aggregator function, like the ones from `IgxPivotNumericAggregate`, `IgxPivotDateAggregate` etc.,  will be restored out of the box. However if you have any custom aggregators (or other custom functions) they need to be set back in the `valueInit`event, for example:
+    ```
+        public onValueInit(value: IPivotValue) {
+        if (value.member === 'AmountOfSale') {
+            value.aggregate.aggregator = IgxTotalSaleAggregate.totalSale;
+        }
+    }
+    ```
+    Same applies to any custom functions on the dimension, like `memberFunction`. If it is a custom function you can set it back on the `dimensionInit` event:
+
+    ```
+     public onDimensionInit(dim: IPivotDimension) {
+        if (dim.memberName === 'AllCities') {
+            dim.memberFunction = () => 'All';
+        }
+    }
+    ```
+    - `igxGridState`:
+    Exposed a `stateParsed` event to the state directive that can be used to additionally modify the grid state before it gets applied.
+
+    ```
+    this.state.stateParsed.subscribe(parsedState => {
+            parsedState.sorting.forEach(x => x.strategy = NoopSortingStrategy.instance());
+        });
+    ```
+
+- `igxGrid`
+    - Added built-in validation mechanism for Grid Editing. Extends the [Angular Form validation](https://angular.io/guide/form-validation) functionality
+        You can configure it in 2 ways:
+        1. Via template-driven configuration on the `igx-column` of the grid:
+            ```html
+            <igx-column required minlength="4" ...>
+            ```
+        2. Via reactive forms using the FormGroup exposed via the `formGroupCreated` event of the grid:
+
+            ```html
+            <igx-grid (formGroupCreated)='formCreateHandler($event)' ...>
+            ```
+
+            ```ts
+            public formCreateHandler(formGr: FormGroup) {
+                // add a validator
+                const prodName = formGr.get('UserName');
+                prodName.addValidators(forbiddenNameValidator(/bob/i))
+            }
+            ```
+
+        Edited cells will enter an invalid state when validation fails and will show an error icon and message. Cell will remain invalid until the value is edited to a valid value or the related state in the validation service is cleared.
+
+        You can refer to the documentation for more details: https://www.infragistics.com/products/ignite-ui-angular/angular/components/grid/validation
+    - Added ability to auto-size columns to the size of their cells and header content on initialization by setting width `auto`:
+    ```
+    <column width='auto' ...>
+    ```
+    - Added support for restoring filtering expressions with custom filtering operands for the `IgxGridStateDirective`.
+    
+
+- 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`.
+
+
+
+### General
+
+- **Breaking Changes** - `filterable` property of `IgxComboComponent` is now deprecated and will be removed in future version. Use `filteringOptions.filterable` instead.
+
+### Theme Changes
+- **Breaking Changes** - `$disable-shadow` property of `IgxTabsComponent` theme has been removed.
+
 ## 14.0.0
 
+- 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. 
+- `IgxDatePicker` and `IgxDateRangePicker` now expose a `weekStart` input property like the `IgxCalendar`
+- `IgxCombo` and  `IgxSimpleComboComponent`
+    - 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`.
+- `IgxDropDown`
+    - The `label` attribute has been changed to `aria-labelledby` and can be set by a latterly added input property `labelledBy`.
+
+### New Features
+- `IgxCombo` and  `IgxSimpleComboComponent`
+    - `filterFunction` input is added. The new property allows changing of the way filtering is done in the combos. By default filtering is made over the values in combo's data when it is a collection of primitive values, or over the values as defined in `displayKey` of the combo. If custom filtering function is provided filtering will be done as specified in the provided function.
+
 ### General
 - Updating dependency to Angular 14
 - `Migrations`
@@ -12,6 +125,15 @@ All notable changes for each version of this project will be documented in this
 - `IgxGridEditingActions`
     - Added new inputs to show/hide the edit and delete buttons - `editRow`, `deleteRow`.
 
+- `IgxTabs`
+    - **Behavioral Change** - Both scroll buttons are displayed when the tabs are not fully visible. When there is no tabs to be scrolled in one of the directions the corresponding scroll button is disabled.
+
+- Locale settings
+    - `IgxDatePicker` and `IgxDateRangePicker` now expose a `weekStart` input property like the `IgxCalendar`
+    - `IColumnPipeArgs` interface now expose a `weekStart` property to control the first week of day in calendar used in the grid for editing and filtering
+    - `locale` property of `IgxCalendar`, `IgxDatePicker`, `IgxDateRangePicker` and `IgxGrid` will now default to globall Angular application locale, if not set.
+    - `weekStart` property of `IgxCalendar`, `IgxDatePicker`, `IgxDateRangePicker` and `IgxGrid` will default to the default first day for the current component `locale`, if not set.
+
 ## 13.2.0
 
 ### General