[Public typings] Consider tightening property typings

[maxpatiiuk]

Check existing issues

• [x] I have checked for existing issues to avoid duplicates

Description

Inline with https://github.com/Esri/calcite-design-system/pull/9915, it appears that Calcite will tighten property typings in a future release.

A few more candidates for tightening to be considered:

• calcite-button.type (currently string, could make it "submit" | "reset" | "button")
• calcite-input.autocomplete, calcite-input-number.autocomplete, calcite-input-text.autocomplete (currently string, could make it AutoFill - it's a built-in TypeScript type)
• calcite-input.enterKeyHint, calcite-input-number.enterKeyHint, calcite-input-text.enterKeyHint (currently string, could make it "enter" | "done" | "go" | "next" | "previous" | "search" | "send") (though, this property is not public)
• calcite-inpuit.inputMode, calcite-input-number.inputMode, calcite-input-text.inputMode (currently string, could make it "none" | "text" | "tel" | "url" | "email" | "numeric" | "decimal" | "search") (though, this property is not public)

(the above tighter types would match Lumina JSX typings; until then, I had to add type assertions in render() to avoid TypeScript errors)

Acceptance Criteria

Consider tightening the types.

Relevant Info

This is what I had to do for now in render():

            <input
              autocomplete={this.autocomplete as LuminaJsx.HTMLElementTags["input"]["autocomplete"]}
              enterKeyHint={enterKeyHint as LuminaJsx.HTMLElementTags["input"]["enterKeyHint"]}
              inputMode={inputMode as LuminaJsx.HTMLElementTags["input"]["inputMode"]}

Which Component

listed above

Example Use Case

No response

Priority impact

impact - p3 - not time sensitive

Calcite package

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

Esri team

ArcGIS Maps SDK for JavaScript

[jcfranco]

Types for autocomplete, inputMode and enterKeyHint won't be necessary since we'll drop these props in favor of the global attributes (see https://github.com/Esri/calcite-design-system/issues/9260 for more info on the last 2 props).