Merge branch 'vnext' into mkirkova/tree-grid-summary-topic

azure-pipelines/build-pipeline-jp+kr.yml

@@ -15,6 +15,10 @@ parameters:
   displayName: 'Get verbose output from steps - where configurable'
   type: boolean
   default: false
+- name: shouldCleanPostExectuion
+  displayName: 'Clean all pipeline dirs after the pipeline finishes?'
+  type: boolean
+  default: true
 
 name: $(BuildDefinitionName)_$(Year:yyyy).$(Month).$(DayOfMonth)$(Rev:.r)
 
@@ -134,4 +138,5 @@ stages:
         targetPath: '$(Build.ArtifactStagingDirectory)'
         artifact: 'XPlatDocFX'
 
-
+    - ${{ if eq(parameters.shouldCleanPostExectuion, true) }}:
+      - task: PostBuildCleanup@4

azure-pipelines/build-pipeline-make-pr-jp+kr.yml

@@ -18,6 +18,10 @@ parameters:
   displayName: 'Get verbose output from steps - where configurable'
   type: boolean
   default: false
+- name: shouldCleanPostExectuion
+  displayName: 'Clean all pipeline dirs after the pipeline finishes?'
+  type: boolean
+  default: true
 
 name: $(BuildDefinitionName)_$(Year:yyyy).$(Month).$(DayOfMonth)$(Rev:.r)
 
@@ -95,3 +99,5 @@ stages:
 
         # Angular doesn't produce an artifact that we can publish right now.
 
+      - ${{ if eq(parameters.shouldCleanPostExectuion, true) }}:
+        - task: PostBuildCleanup@4

azure-pipelines/build-pipeline-make-pr.yml

@@ -18,6 +18,10 @@ parameters:
   displayName: 'Get verbose output from steps - where configurable'
   type: boolean
   default: false
+- name: shouldCleanPostExectuion
+  displayName: 'Clean all pipeline dirs after the pipeline finishes?'
+  type: boolean
+  default: true
 
 name: $(BuildDefinitionName)_$(Year:yyyy).$(Month).$(DayOfMonth)$(Rev:.r)
 
@@ -93,3 +97,5 @@ stages:
 
       # Angular doesn't produce an artifact that we can publish right now.
 
+      - ${{ if eq(parameters.shouldCleanPostExectuion, true) }}:
+        - task: PostBuildCleanup@4

azure-pipelines/build-pipeline.yml

@@ -16,6 +16,10 @@ parameters:
   displayName: 'Get verbose output from steps - where configurable'
   type: boolean
   default: false
+- name: shouldCleanPostExectuion
+  displayName: 'Clean all pipeline dirs after the pipeline finishes?'
+  type: boolean
+  default: true
 
 name: $(BuildDefinitionName)_$(Year:yyyy).$(Month).$(DayOfMonth)$(Rev:.r)
 
@@ -102,3 +106,6 @@ stages:
           language: en
           isVerbose: ${{ parameters.isVerbose }}
           workingDir: '$(Build.SourcesDirectory)'
+
+      - ${{ if eq(parameters.shouldCleanPostExectuion, true) }}:
+        - task: PostBuildCleanup@4

doc/en/components/charts/chart-overview.md

@@ -51,7 +51,7 @@ We make {Platform} Category and Financial Chart easier to use, the good news you
 
 The {Platform} Bar Chart, or Bar Graph is among the most common category chart types used to quickly compare frequency, count, total, or average of data in different categories with data encoded by horizontal bars of equal width and differing lengths. They are ideal for showing variations in the value of an item over time, data distribution, sorted data ranking (high to low, worst to best). Data is represented using a collection of rectangles that extend from the left to right of the chart towards the values of data points. Learn more about our [bar chart](types/bar-chart.md)
 
-`sample="/charts/data-chart/bar-chart-multiple-sources", height="600", alt="{Platform} Bar Chart Multiple Sources"`
+`sample="/charts/data-chart/bar-chart-multiple-sources", img-src="https://static.infragistics.com/marketing/Website/products/Ignite-UI-for-Angular/ignite-ui-angular-bar-chart", height="600", alt="{Platform} Bar Chart Multiple Sources"`
 
 
 

doc/en/components/charts/types/treemap-chart.md

@@ -2,7 +2,7 @@
 title: {Platform} Treemap | Data Visualization Tools | Orientation | Layout | Data Binding | Infragistics
 _description: Use Infragistics' {Platform} Treemap control show relative weighting of data points at more than one level supporting strip, squarified, and slice-and-dice algorithms. Learn about {ProductName} treemap!
 _keywords: {Platform} Tree Map, Treemap, layout, orientation, {ProductName}, Infragistics
-mentionedTypes: ["Treemap", "TreemapOrientation", "TreemapLayoutType"]
+mentionedTypes: ["Treemap", "TreemapOrientation", "TreemapLayoutType", "TreemapHighlightingMode", "TreemapHighlightedValueDisplayMode"]
 namespace: Infragistics.Controls.Charts
 ---
 # {Platform} Treemap
@@ -102,13 +102,13 @@ In the following example, the treemap demonstrates the ability of node highlight
 
 ## {Platform} Treemap Percent based highlighting 
 
-`HighlightedItemsSource`: Specifies the datasource to read highlighted values from. If null, then highlighted values are read from the ItemsSource property.
-`HighlightedValueMemberPath`: Specifies the name of the property in the datasource where the highlighted values are read.
-`HighlightedValueOpacity`: Controls the opacity of the normal value behind the highlighted value.
-`HighlightedValuesDisplayMode`: Enables or disables highlighted values.
- - Auto: The treemap decides what mode to use.
- - Overlay: The treemap displays highlighted values over top the normal value with a slight opacity applied to the normal value.
- - Hidden: The treemap does not show highlighted values.
+- `HighlightedItemsSource`: Specifies the datasource to read highlighted values from. If null, then highlighted values are read from the ItemsSource property.
+- `HighlightedValueMemberPath`: Specifies the name of the property in the datasource where the highlighted values are read.
+- `HighlightedValueOpacity`: Controls the opacity of the normal value behind the highlighted value.
+- `HighlightedValuesDisplayMode`: Enables or disables highlighted values.
+    - Auto: The treemap decides what mode to use.
+    - Overlay: The treemap displays highlighted values over top the normal value with a slight opacity applied to the normal value.
+    - Hidden: The treemap does not show highlighted values.
 
 `sample="/charts/tree-map/highlighting-percent-based", height="600", alt="{Platform} Treemap Percent based Highlighting"`
 
@@ -127,4 +127,6 @@ The following is a list of API members mentioned in the above sections:
 
 - `Treemap`
 - `LayoutOrientation`
+- `HighlightedValuesDisplayMode`
+- `HighlightedValueMemberPath`
 - `LayoutType`

doc/en/components/grids/_shared/multi-column-headers.md

@@ -110,7 +110,6 @@ The declaration of multi-column headers is achieved by wrapping a set of columns
     </IgrColumnGroup>
 </{ComponentSelector}>
 ```
-
 <!-- ComponentEnd: TreeGrid -->
 
 <!-- ComponentStart: HierarchicalGrid -->
@@ -303,7 +302,6 @@ For achieving `n-th` level of nested headers, the declaration above should be fo
     </IgrColumnGroup>
 </{ComponentSelector}>
 ```
-
 <!-- ComponentEnd: TreeGrid -->
 
 <!-- ComponentStart: HierarchicalGrid -->

doc/en/components/grids/_shared/selection.md

@@ -63,9 +63,9 @@ Property `CellSelection` enables you to specify the following options:
 - `Single` - Selection of only one cell within the `{ComponentName}` would be available.
 - `Multiple` - Currently, this is the default state of the selection in the `{ComponentName}`. Multi-cell selection is available by mouse dragging over the cells, after a left button mouse clicked continuously.
 
-<!-- ComponentStart:  Grid -->
+<!-- ComponentStart:  Grid, TreeGrid, HierarchicalGrid -->
 > Go to [Cell selection topic](cell-selection.md) for more information.
-<!-- ComponentEnd:  Grid -->
+<!-- ComponentEnd:  Grid, TreeGrid, HierarchicalGrid -->
 
 ### {Platform} {ComponentTitle} Column Selection
 
@@ -77,9 +77,9 @@ This leads to the following three variations:
 - Multi column selection - holding <kbd>ctrl</kbd> + <kbd>mouse click</kbd> over the column cells.
 - Range column selection - holding <kbd>shift</kbd> + <kbd>mouse click</kbd> selects everything in between.
 
-<!-- ComponentStart:  Grid -->
+<!-- ComponentStart:  Grid, TreeGrid, HierarchicalGrid -->
 > Go to [Column selection topic](column-selection.md) for more information.
-<!-- ComponentEnd:  Grid -->
+<!-- ComponentEnd:  Grid, TreeGrid, HierarchicalGrid -->
 
 <!-- ComponentStart: Grid -->