v3 - optional labels

I have a use-case where labels are part of a field it self and are controlled by field because of design requirements. So I would like to have a way to remove label rendering completely.

I saw that in new version you are offering usage of label templating with slots. But even if slot is empty you still render label tag. So for someone to remove label it has to remove it in schema currently.

I would suggest you make some additional form option or something that would indicate what parts of “general” layout should be rendered.

Current workaround is to ditch label in schema and introduce some other custom property that would act like one.

[gapipro]

Yep thats exactly what I have done. Thanks for help.

[zoul0813]

think of label as a reserved property, that is common and shared across all VFG fields. You can introduce a new custom property called “labelText” or “customComponentLabel” (where “customComponent” would be the name of your component … so the field is specific to your component.

I believe v3 is introducing a standard “property bucket” called “attributes” or something similar … where custom components can place any extra bits, without overriding VFG core fields.

For example …

{
  "type": "customComponent",
  "model": "model",
  "attributes": {
    "label": "custom label for your component to use"
  }
}

You can also change “attributes” to be the name of your custom component, and store any necessary properties your component needs in this object … keeping your components custom properties scoped to itself, without littering the fields common scope properties.