Color Picker is currently setting the value for both calcite-input and its internal input in handleChannelInput. We should figure out why it needs to do that and refactor it if possible.
Proposed Advantages
Updating component's internals is an anti pattern. It is effectively going into the shadowRoot. Setting the value of the calcite-input should update its internals. We may need a lifecycle methods refactor for calcite-input.
This PR (will) remove the deprecated nativeEvent event payload in favor of an intenal Input method to make sure Color Picker doesn't break. This is a temporary change until we can refactor, since we need to move all of the deprecations now
Description
Color Picker is currently setting the value for both
calcite-input
and its internalinput
inhandleChannelInput
. We should figure out why it needs to do that and refactor it if possible.Proposed Advantages
Updating component's internals is an anti pattern. It is effectively going into the shadowRoot. Setting the value of the
calcite-input
should update its internals. We may need a lifecycle methods refactor forcalcite-input
.Which Component
calcite-input
(mostly)calcite-color-picker
Relevant Info
Here is a comment with some context https://github.com/Esri/calcite-components/pull/5908#discussion_r1040562755
This PR (will) remove the deprecated
nativeEvent
event payload in favor of an intenal Input method to make sure Color Picker doesn't break. This is a temporary change until we can refactor, since we need to move all of the deprecations now6099