Supported Attributes for the Property Tag in the js-meta.xml File
The js-meta.xml file for a custom Lightning web component can have the targetConfig of lightningCommunity__Default. In this case, certain attributes for the property tag have additional considerations when they're used with a property that references a custom property type.
These are the attributes that you can use for the property tag.
- name
- type
- datasource
- default
- description
- exposedTo
- filter
- label
- max
- min
- placeholder
- required
- screenResponsive
Here are the implications of using some of these attributes with a property that references a custom property type.
| Attribute | Implications |
|---|---|
type | Salesforce supports five standard property types for Lightning web components in Experience Builder: String, Integer, Boolean, ContentReference, and Color. You can use all these types together with properties that reference custom property types. If the Lightning web component is used in a site or managed package, you can update the type value if the original value references an ExperiencePropertyTypeBundle or a custom LightningTypeBundle and the updated value is referencing a custom LightningTypeBundle. Check to be sure there are no breaking changes in the schema of the new type. (For information on breaking changes, see Object-Based Custom Lightning Types Modification Guidelines in the Lightning Types Developer Guide.) |
exposedTo | This attribute is required if you use the screenResponsive attribute. The valid value is css. This feature works for LWR sites only. |
screenResponsive | For properties that reference custom property types that have an underlying JSON schema type of string, integer, or number, you can specify this attribute to indicate whether the property is screen responsive. This feature works for LWR sites only. |
translatable | When you specify translatable="true", you indicate that this component property can hold different values for each language that you support in your Experience Cloud site. You can specify the translatable attribute in a property tag only when the custom property type that's being referenced has an underlying JSON schema type of string. For example, you can add translatable="true" to properties that reference these types. lightning__textType lightning__multlineTextType lightning__richTextType lightning__urlType lightning__dateType When you specify translatable="true" for a property of type="lightning__richTextType", the property's value is exported in rich text format in the .xlf file via the Export Content feature in Experience Builder. All other types are exported as plain text. |
See Also