Skip to content
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

Bug fixes and button updates #53

Merged
merged 2 commits into from
Feb 1, 2024
Merged

Conversation

AnthonMS
Copy link
Owner

@AnthonMS AnthonMS commented Feb 1, 2024

Description

Bug fixes and major changes to my-button, so be aware of those when updating while using that card.

my-button has had an overhaul on the default styling. This might cause styling issues with users already using it and styling it. There might be more default styling that has to be changed by that custom styling as well now.
However, I think the default look of it is better, it is using theme colors as default now.
It also supports the switch entity now. slider is not shown as default for switches but can be toggled.

Related Issue

#49 fixed
#27 fixed

Motivation and Context

It solves the issues everyone is having with my-slider-v2 with step option. And adding new functionality that might be useful for some.

How Has This Been Tested

Extensively locally, but I don't have all the entity types to make sure the new changes work on fans and such.

Types of changes

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • 🚀 New feature (non-breaking change which adds functionality)
  • 🌎 Translation (addition or update a translation)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have tested the change locally.

#49 allowTapping false not working has been fixed. And a new config key has been added 'marginOfError'. It is 10 default. marginOfError is amount of pixels the input can be from the thumb.
#27 No step option has been fixed. There has always been a step option, just very broken logic. It has been fixed and the slider will now only update to closest step.
allowSliding will allow the user to slide in the direction of the slider for an amount of pixels and start sliding. This is in conjuction with allowTapping false so you can start sliding anywhere on the slider card and when you surpass the distance it will activate.
slideDistance is the other new config key. This is default 10. It determines the amount of pixels the input has the travel for allowSliding to take effect.
@AnthonMS AnthonMS self-assigned this Feb 1, 2024
@AnthonMS AnthonMS merged commit afab638 into main Feb 1, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant