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
I find it a little weird that label details are hardcoded into label instead of being a separate component.
Currently, there is no way to remove or rearrange label details from the label without rewriting the whole label components.
Was there a particular reason to having them bundled together?
If not, can we have them separated into label and label_details, to allow for greater customizability?
The text was updated successfully, but these errors were encountered:
I agree but we'd need to add support for different gaps between components. I'd imagine it'd work like gap = { 0, 1 } (components a and b have no gap, components b and c have gap of 1). PR is welcome if you're interested in working on this
Ahh, so it was because you preferred to not have any gaps between the label and label details. { { "label", "label_details", "label_description" } } removes the gap between the details and the description,
While { { "label", "label_details" }, { "label_description" } } sends the description to the next alignment column.
One way to work around this without reworking gap is to add a "space" component, which does nothing but return a single space.
Alternatively, simply including a detail-less version of label in the plugin would make it a lot convenient to customize, although this would be adding an unused code for a potential niche (no idea how many people will want to rearrange label details) use case.
Feature Description
I find it a little weird that label details are hardcoded into
label
instead of being a separate component.Currently, there is no way to remove or rearrange label details from the
label
without rewriting the whole label components.Was there a particular reason to having them bundled together?
If not, can we have them separated into
label
andlabel_details
, to allow for greater customizability?The text was updated successfully, but these errors were encountered: