Optional
aliasArray with the list of child XML fragments that match this metadata type
Optional
childrenType definitions for child types, if the type has any.
Examples: CustomField
and CompactLayout
on CustomObject
Optional
directories?: DirectoryIndexName of the directory where components are located in a package.
Optional
folderIf the type is a folder type (container for components), the id of the type it is a container for.
Optional
folderIf the type is contained in folders, the id of the type that contains it.
True when the metadata has a separate content file(s) this implies that any -meta.xml file is a meta file and not a content file and should not be renamed.
Unique identifier of the metadata type. Usually the API name lowercased.
Optional
ignoreIf the parent name should be ignored when constructing the type's fullName
Optional
ignoreWhether or not to ignore the fullName that's parsed from the file path. If true, the metadata type's name will be used instead. For example, CustomLabels instead of MyLabels.
Optional
inWhether or not components are stored in folders.
Examples: Reports, Dashboards, Documents, EmailTemplates
use folderType
to get the related folder type, if one exists
Optional
isWhether the component is supported by the Metadata API and therefore should be included within a manifest.
Optional
legacyWhen converting deploying source, this will update the suffix in the output or temporary directory (metadata format) Use this, along with additional suffix keys in the registry, to support incorrect suffixes from existing code
Optional
metaMetaFile suffix
An override to the default "-meta.xml" suffix.
Examples: "_meta.json" for DigitalExperience.
API name of the metadata type.
Optional
strategiesConfiguration for resolving and converting components of the type.
Optional
decomposition?: "topLevel" | "folderPerType"Optional
recomposition?: "startEmpty"Optional
transformer?: "standard" | "decomposed" | "staticResource" | "nonDecomposed" | "decomposedLabels"Optional
strictWhether or not components are required to reside in a folder named after the type's directoryName.
Optional
suffixFile suffix
Some types may not have one, such as those made up of varying file extensions.
Examples: LightningComponentBundles, Documents, StaticResources
Optional
supportsWhether the component can be partially deleted, such as metadata types that are made up of multiple files.
Examples: LightningComponentBundle
, ExperienceBundle
, StaticResource
, and DigitalExperienceBundle
Optional
supportsWhether or not components of the same type can be can be specified with the wildcard character, and by name in a manifest
<members>*</members>
<members>Account</members>
<name>CustomObject</name>
Optional
unaddressableWhether the component requires the parent to be present when deploying/retrieving
Optional
uniqueThe xml attribute used as the unique identifier when parsing the xml
Optional
xmlThe XML element name for the type in the xml file used for constructing child components.
Name of the XML tag used for this metadata type
Use name instead
Whenever this type is requested, return the aliasFor type instead