Refactor-out usages of Stencil's "readTask"

[maxpatiiuk]

Description

In 3 files, Calcite uses Stencil's readTask() function.

Could you check if there was a particular reason readTask was used or was it just a performance micro optimization?

Lit's default re-render scheduling is very simple - they don't provide readTask/writeTask. However, they expose hook for customizing the scheduling, letting you implement your own alternatives of Stencil's readTask/writeTask if it is important to have them.

Stencil's readTask/writeTask is a smart performance optimization, but it's hardly used - no usages at Esri outside of Calcite, and Calcite has only 3 usages.

TODO:

• check if readTask() is needed
• if not, refactor out it's usages

Proposed Advantages

Compatibility with Lit's default scheduling system

Which Component

3 files:

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

  Line 14 in 7fe1601

  readTask,

• calcite-design-system/packages/calcite-components/src/components/tab-nav/tab-nav.tsx

  Line 10 in 7fe1601

  readTask,

• calcite-design-system/packages/calcite-components/src/utils/openCloseComponent.ts

  Line 1 in 7fe1601

  import { readTask } from "@stencil/core";

Relevant Info

No response

Calcite package

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