docs

Manifest for Components (Inside Libraries)

The manifest (also known as descriptor) for components contains a subset of the attributes in the manifest for applications

Attributes in the sap.app namespace

Attribute Comment
`id` Mandatory
`type` With value `component`; mandatory
`i18n` Optional attribute: A URL string to the properties file that contains the text symbols for the manifest; the URL is interpreted relative to the `manifest`. Alternatively, an object defined as described in [Terminologies](/docs/04_Essentials/terminologies-eba8d25.html). If the manifest contains placeholders in `` syntax but no `i18n` attribute has been provided, the default value `i18n/i18n.properties` is used to request a ResourceBundle.
`embeddedBy` Mandatory, for example, `"../"`
`title` Mandatory
`subTitle`
`description`
`ach`
`dataSources`
`cdsViews`
`resources` Mandatory; must have value `resources.json` as file; it is generated by the library build with this name
`offline`
`sourceTemplate`

Attributes in the sap.ui namespace

Attribute Comment
`technology` With value `UI5`; mandatory
`deviceTypes`
`supportedThemes`

Attributes in the sap.ui5 namespace

Attribute Comment
`resources`
`dependencies` `libs` `components`
`models`
`rootView`
`handleValidation`
`config`
`routing`
`extends` `component` `minVersion`
`contentDensities`
`componentName`

Attributes in the sap.mobile namespace

Attribute Comment
`definingRequests`

Library Name Determination

SAPUI5 determines the library name by analyzing the component namespace (package) up to the part where the segment starts with a capitalized letter. If the library name that has been determined, does not fit your component, an additional library attribute needs to be filled in the component metadata in Component.js to specify the library your component belongs to.

Example:


sap.ui.core.UIComponent.extend("com.sap.fancylibrary.sub.CompLib.Component", {
    metadata : {
        "manifest" : "json",
        "library" : "com.sap.fancylibrary",
    ...
}