Skip to content

Commit 6da286a

Browse files
Svetoslav KrastevSvetoslav Krastev
authored andcommitted
Merge master into skrastev/task-12417-master
2 parents 05b5475 + 2cde0ce commit 6da286a

File tree

220 files changed

+7538
-7428
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

220 files changed

+7538
-7428
lines changed

.eslintrc.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@
2626
],
2727
"no-unused-vars": "off",
2828
"@typescript-eslint/no-unused-vars": [
29-
"warn",
29+
"error",
3030
{
3131
"varsIgnorePattern": "_",
3232
"argsIgnorePattern": "^_"

.github/CONTRIBUTING.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -21,15 +21,16 @@ When working on an issue for the Ignite UI for Angular repository, you need to b
2121
## Development - applicable to issues
2222

2323
### 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.
3334

3435
Example status workflows:
3536

.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
name: Bug report
33
about: Create a report to help us improve
44
title: ''
5-
labels: ':bug: bug'
5+
labels: ':bug: bug,:new: status: new'
66
assignees: ''
77
projects: 'IgniteUI/16'
88

.github/ISSUE_TEMPLATE/feature_request.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
name: Feature request
33
about: Suggest an idea for this project
44
title: ''
5-
labels: ':toolbox: feature-request'
5+
labels: ':toolbox: feature-request,:new: status: new'
66
assignees: ''
77
projects: IgniteUI/16
88

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,7 @@ npm-debug.log
3838
yarn-error.log
3939
testem.log
4040
/typings
41+
TESTS-**.xml
4142

4243
# System Files
4344
.DS_Store

CHANGELOG.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,8 @@ All notable changes for each version of this project will be documented in this
2323
* - `IgxColumnComponent` - `ColumnType` (for example the column parameter in `igxFilterCellTemplate`)
2424
* - `IgxGridCell` - `CellType` (for example the cell parameter in `igxCell` template)
2525

26+
- A new `groupRecord` parameter has been exposed in `operate` method, that is an `IGroupByRecord` object describing the grouped row in case grouping is applied.
27+
2628
- `excelStyleHeaderIconTemplate` - Gets/Sets the excel style header icon.
2729
- `groupRowTemplate` - Gets/Sets the template reference for the group row.
2830
- `headSelectorTemplate` - Gets/Sets the header row selector template.
@@ -58,6 +60,9 @@ All notable changes for each version of this project will be documented in this
5860
- `multi` mode - select/deselect all dates between the last selected/deselected and the one clicked while holding `Shift`.
5961
- `range` mode - extend/shorten the range from the last selected date to the one clicked while holding `Shift`.
6062

63+
- `IgxFilterOptions`
64+
- Added support for multiple keys.
65+
6166
### Theme Changes
6267
- **Breaking Changes** - The `palette` function no longer provides `info`, `success`, `warn` and `error` colors. Therefore you have to pass custom values for them if you need to use these colors. You can also use the values for `info`, `success`, `warn` and `error` colors from our predefined color palettes.
6368

ROADMAP.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@
22

33
# Current Milestone
44

5-
## Milestone 24, version 15.0 (Due by Nov, 2022)
5+
## Milestone 25, version 15.0 (Due by Jan, 2023)
66

7-
1. **[DONE]** Support exporting grid with summaries [#11598](https://github.com/IgniteUI/igniteui-angular/issues/11598)
8-
2. **[DONE]** Themes: Add support for adjusting spacing via CSS vars [#11368](https://github.com/IgniteUI/igniteui-angular/issues/11368)
9-
3. Support for Angular 15
7+
1. Design update of Combo Component
8+
2. Design update of Input Group Component
9+
3. Design update of List Component
1010

1111
## Going down the road
1212

@@ -20,6 +20,12 @@
2020

2121
# Previous Milestone
2222

23+
## Milestone 24, version 15.0 (Due by Nov, 2022) [Release Blog](https://www.infragistics.com/community/blogs/b/infragistics/posts/ignite-ui-december-release-2022)
24+
25+
1. **[DONE]** Support exporting grid with summaries [#11598](https://github.com/IgniteUI/igniteui-angular/issues/11598)
26+
2. **[DONE]** Themes: Add support for adjusting spacing via CSS vars [#11368](https://github.com/IgniteUI/igniteui-angular/issues/11368)
27+
3. **[DONE]** Support for Angular 15
28+
2329
## Milestone 24, version 14.2 (Released October 06th, 2022) [Release Blog 22.2](https://www.infragistics.com/community/blogs/b/infragistics/posts/ignite-ui-for-angular-22-2)
2430

2531
1. **[DONE]** Angular query builder component (Angular Tree Grid Advanced Filtering without the tree grid) [#11750](https://github.com/IgniteUI/igniteui-angular/issues/11750)

azure-pipelines.yml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -58,8 +58,8 @@ steps:
5858
testRunner: 'JUnit'
5959
testResultsFiles: '**/TESTS-*.xml'
6060

61-
# - task: PublishCodeCoverageResults@1
62-
# inputs:
63-
# codeCoverageTool: Cobertura
64-
# summaryFileLocation: '$(System.DefaultWorkingDirectory)/coverage/cobertura-coverage.xml'
65-
# reportDirectory: '$(System.DefaultWorkingDirectory)/coverage'
61+
- task: PublishCodeCoverageResults@1
62+
inputs:
63+
codeCoverageTool: Cobertura
64+
summaryFileLocation: '$(System.DefaultWorkingDirectory)/coverage/cobertura-coverage.xml'
65+
reportDirectory: '$(System.DefaultWorkingDirectory)/coverage'

e2e/cypress/plugins/index.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
11
// Plugins enable you to tap into, modify, or extend the internal behavior of Cypress
22
// For more info, visit https://on.cypress.io/plugins-api
3-
module.exports = (on, config) => {}
3+
module.exports = (_on, _config) => {}

0 commit comments

Comments
 (0)