feat: add ability to pass options to setValue
calls
#2894
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One of the most requested features is finally here. Behind this abstract title hides the possibility to use transition durations in the
setValue
API. Example:The method has gained a third optional argument, which is an options bag for the underlying calls. Each
setValue
implementation will choose the options it understands, so the object can be configured in one location and reused for all calls.For now, this only supports the
transitionDuration
option, but allows us to add more in the future.fixes: #1321
fixes: home-assistant/core#46234
fixes: home-assistant/core#48470
related: zwave-js/zwave-js-ui#1159