Consistently name custom element classes

[maxpatiiuk]

Check existing issues

• I have checked for existing issues to avoid duplicates

Description

Most Calcite custom element class names don't start with Calcite:

calcite-design-system/packages/calcite-components/src/components/button/button.tsx

Line 53 in 1cde584

export class Button

However, 5 classes do start with Calcite prefix:

• CalciteMenu

  • calcite-design-system/packages/calcite-components/src/components/menu/menu.tsx

    Line 29 in 1cde584

    export class CalciteMenu extends LitElement implements LoadableComponent {

• CalciteMenuItem
• CalciteNavigation
• CalciteNavigationLogo
• CalciteNavigationUser

Acceptance Criteria

Every class name starts or does not start with Calcite for consistency.

Relevant Info

While not a promoted use case, these class names may be imported directly in consumer apps (rather than HTMLCalciteMenuElement), so the rename would be a breaking change.

Which Component

5 components listed above

Example Use Case

No response

Priority impact

impact - p3 - not time sensitive

Calcite package

• @esri/calcite-components
• @esri/calcite-components-react
• @esri/calcite-design-tokens
• @esri/eslint-plugin-calcite-components

Esri team

ArcGIS Maps SDK for JavaScript