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 Button component currently has a buttonType prop which allows the consumer to pass in the class name of the Bootstrap button to use (e.g., primary, link, etc.). This value is prefixed with btn- and added to the list of class names.
However, we also have a type prop which represents the actual type of the button (i.e., submit, reset, button). Having both of these props is confusing as buttonType does not actually represent a type of button as it's used as a class name.
Instead, we should deprecate the buttonType prop and have consumers of the Button component pass in the Bootstrap class name (e.g., .btn-primary) in the className prop.
The
Button
component currently has abuttonType
prop which allows the consumer to pass in the class name of the Bootstrap button to use (e.g., primary, link, etc.). This value is prefixed withbtn-
and added to the list of class names.However, we also have a
type
prop which represents the actual type of the button (i.e., submit, reset, button). Having both of these props is confusing asbuttonType
does not actually represent a type of button as it's used as a class name.Instead, we should deprecate the
buttonType
prop and have consumers of theButton
component pass in the Bootstrap class name (e.g.,.btn-primary
) in theclassName
prop.Note: This would be a breaking change.
cc: @georgebabey
The text was updated successfully, but these errors were encountered: