BREAKING CHANGE: refactor labeled
Button API
#616
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.
Fixes #510
This PR makes the Button
labeled
API consistent with the Inputlabeled
API. Previously, a Button could be used as alabeled button
wrapper with another Button/Label child. Now:labeled
is nowlabelPosition
label
prop to pass the Label.Fixes #612
It also fixes a recent regression, renderinglabeled
Buttons as<button>
tags. You cannot nest a<button>
in a<button>
, the labeled button must be adiv
so it can contain a Label and a Button (<button>
) component.This did not account for
labelPosition
with anicon
. In that case, a<button>
can contain an<i />
. Adiv
is only required when there is alabel
. A fix commit has been made to master, TechnologyAdvice/stardust@3379aa5, and will be included in this release.