refactor(charts): explicitly define change detection strategy

[spliffone]

---

Documentation.
Examples.
Dashboards Demo.
Playwright report.

Coverage Reports:

• charts-ng
• dashboards-ng
• element-ng
• element-translate-ng
• maps-ng
• native-charts-ng

[gemini-code-assist]

Code Review

This pull request explicitly configures several chart components and test hosts to use ChangeDetectionStrategy.Default and imports the strategy accordingly. The reviewer correctly points out that since Default is already the default change detection strategy in Angular, explicitly defining it is redundant and adds unnecessary boilerplate. It is recommended to remove these redundant imports and configuration properties across all modified files to keep the codebase clean and aligned with the style guide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Explicitly importing ChangeDetectionStrategy is unnecessary if we are not using it. Since Default is the default strategy in Angular, we can omit it entirely.

Suggested change

	import { ChangeDetectionStrategy, Component, input, OnChanges, SimpleChanges } from '@angular/core';
	import { Component, input, OnChanges, SimpleChanges } from '@angular/core';

[gemini-code-assist]

In Angular, ChangeDetectionStrategy.Default is the default strategy. Explicitly defining it is redundant and adds unnecessary boilerplate. It is cleaner to omit it.

  styleUrl: '../common/si-chart-base.component.scss'

References

1. The style guide states that changeDetection: ChangeDetectionStrategy.OnPush should be set for newly added components, but existing components should not be flagged. Explicitly setting ChangeDetectionStrategy.Default on existing components is redundant and adds unnecessary boilerplate. ^(link)

[gemini-code-assist]

Explicitly importing ChangeDetectionStrategy is unnecessary if we are not using it. Since Default is the default strategy in Angular, we can omit it entirely.

Suggested change

	import { ChangeDetectionStrategy, Component } from '@angular/core';
	import { Component } from '@angular/core';

[gemini-code-assist]

In Angular, ChangeDetectionStrategy.Default is the default strategy. Explicitly defining it is redundant and adds unnecessary boilerplate. It is cleaner to omit it.

  styleUrl: '../common/si-chart-base.component.scss'

References

1. The style guide states that changeDetection: ChangeDetectionStrategy.OnPush should be set for newly added components, but existing components should not be flagged. Explicitly setting ChangeDetectionStrategy.Default on existing components is redundant and adds unnecessary boilerplate. ^(link)

[gemini-code-assist]

Explicitly importing ChangeDetectionStrategy is unnecessary if we are not using it. Since Default is the default strategy in Angular, we can omit it entirely.

Suggested change

	import { ChangeDetectionStrategy, Component, SimpleChange, viewChild } from '@angular/core';
	import { Component, SimpleChange, viewChild } from '@angular/core';

[gemini-code-assist]

In Angular, ChangeDetectionStrategy.Default is the default strategy. Explicitly defining it is redundant and adds unnecessary boilerplate. It is cleaner to omit it.

  styleUrl: '../common/si-chart-base.component.scss'

References

1. The style guide states that changeDetection: ChangeDetectionStrategy.OnPush should be set for newly added components, but existing components should not be flagged. Explicitly setting ChangeDetectionStrategy.Default on existing components is redundant and adds unnecessary boilerplate. ^(link)

[gemini-code-assist]

Explicitly importing ChangeDetectionStrategy is unnecessary if we are not using it. Since Default is the default strategy in Angular, we can omit it entirely.

Suggested change

	import { ChangeDetectionStrategy, Component, SimpleChange, viewChild } from '@angular/core';
	import { Component, SimpleChange, viewChild } from '@angular/core';

[gemini-code-assist]

In Angular, ChangeDetectionStrategy.Default is the default strategy. Explicitly defining it is redundant and adds unnecessary boilerplate. It is cleaner to omit it.

  `

[gemini-code-assist]

Explicitly importing ChangeDetectionStrategy is unnecessary if we are not using it. Since Default is the default strategy in Angular, we can omit it entirely.

Suggested change

	import { ChangeDetectionStrategy, Component, input } from '@angular/core';
	import { Component, input } from '@angular/core';

[gemini-code-assist]

In Angular, ChangeDetectionStrategy.Default is the default strategy. Explicitly defining it is redundant and adds unnecessary boilerplate. It is cleaner to omit it.

  styleUrl: '../common/si-chart-base.component.scss'

References

1. The style guide states that changeDetection: ChangeDetectionStrategy.OnPush should be set for newly added components, but existing components should not be flagged. Explicitly setting ChangeDetectionStrategy.Default on existing components is redundant and adds unnecessary boilerplate. ^(link)