-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some properties (e.g. inputMode
not available anymore)
#9235
Comments
Closing out the above as the global attributes are provided and the issue for Maps SDK for JS appears to be related to the maquette VDOM library typings for globals. |
One thing that #9123 overlooked was how our custom global component prop's were using the kebabified™ case vs the native ones. I think we can add props ( |
Reopening to provide support to kebab-case per Franco's comment above. |
…-mode` and `input-mode` attributes (#9245) **Related Issue:** #9235 ## Summary This fixes the following issues introduced by #9123 when component props that shadowed global attributes were removed: * the kebab-cased attribute names of those props would no longer work (namely, `enter-key-mode`, `input-mode`) * `autofocus` was missing from component types as Stencil does not include it in the base `HTMLAttribute` type (see ionic-team/stencil#5726).
…-mode` and `input-mode` attributes (#9245) (#9306) **Related Issue:** #9235 ## Summary This fixes the following issues introduced by #9123 when component props that shadowed global attributes were removed: * the kebab-cased attribute names of those props would no longer work (namely, `enter-key-mode`, `input-mode`) * `autofocus` was missing from component types as Stencil does not include it in the base `HTMLAttribute` type (see ionic-team/stencil#5726). Co-authored-by: Ben Elan <[email protected]>
🍡 Verified locally on |
…n HTMLElement (#9343) **Related Issue:** #9235 ## Summary Exposes `autofocus` property to ensure the prop/attr is available on the `HTMLElement` type. This should no longer be necessary once ionic-team/stencil#5726 is fixed and available in Stencil.
Reopening due to cc @AdelheidF |
Installed and assigned for verification. |
…n HTMLElement (#9343) **Related Issue:** #9235 ## Summary Exposes `autofocus` property to ensure the prop/attr is available on the `HTMLElement` type. This should no longer be necessary once ionic-team/stencil#5726 is fixed and available in Stencil.
…n HTMLElement (#9343) (#9347) **Related Issue:** #9235 ## Summary Exposes `autofocus` property to ensure the prop/attr is available on the `HTMLElement` type. This should no longer be necessary once ionic-team/stencil#5726 is fixed and available in Stencil. Co-authored-by: JC Franco <[email protected]>
Verified with https://github.com/jcfranco/cc-autofocus-missing-from-types in |
Check existing issues
Actual Behavior
While testing the latest v2.8.0 of Calcite Components together with the JSAPI, the Typescript compiler reported that
inputMode
is no longer available as a property of<calcite-input-number>
. It seems like the change got introduced by 13ba953 and it could affect apps using that property or any of the other properties that were removed.Expected Behavior
Typings should still contain the previously-existing properties. Alternatively, a breaking change and consequent major version should be released.
Reproduction Sample
https://codepen.io/hccampos/pen/ExJzRRq
Reproduction Steps
$0.inputMode
in the console and notice that theinputMode
property isn't set.Alternatively, build an application which makes use of the typings and notice that the property isn't available.
Reproduction Version
2.8.0
Relevant Info
No response
Regression?
2.7.x
Priority impact
p0 - emergency
Impact
While it doesn't directly impact my team (we haven't decided if we'll upgrade to this version of Calcite for the upcoming release), it can potentially affect any application which was using one of the removed properties. Their builds can fail and the components may not work as expected.
Calcite package
Esri team
ArcGIS Maps SDK for JavaScript
The text was updated successfully, but these errors were encountered: