You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The library currently supports a custom css class that goes along with range-slider in the root/wrapper element. This issue is more about allowing developer to completely replace all range-sliders classes with custom ones.
Motivation
Allowing developers to completely replaces the default css variables allows them to:
Support CSS Modules
Have more granular control
Avoid collisions (e.g. an app could already have a global range-slider class for something else)
Suggestion
Replace the className props with a classNames prop that accepts an object
The library currently supports a custom css class that goes along with
range-slider
in the root/wrapper element. This issue is more about allowing developer to completely replace allrange-slider
s classes with custom ones.Motivation
Allowing developers to completely replaces the default css variables allows them to:
range-slider
class for something else)Suggestion
Replace the
className
props with aclassNames
prop that accepts an objectclassNames
should be optional as well as the keys, and default to the current classes.The text was updated successfully, but these errors were encountered: