Migrating from Component Metadata to Descriptor

Overview, how the component metadata are mapped to the descriptor.

For compatibility reasons, the mapping to the manifest.json file is done automatically. If a metadata property has been defined, it can also be consumed via the corresponding property of the manifest.json file. For a detailed step-by-step guide, see Creating a Descriptor File for Existing Apps.

Note To benefit from the performance improvements that can be achieved by using “manifest first”, we recommend to migrate the component metadata to the descriptor (manifest.json). For more information about manifest first, see the Manifest First Function section in Descriptor for Applications, Components, and Libraries.

Mapping Table
Metadata	Descriptor	Comment
Component namespace	`sap.app/id`	-
`version`	`sap.app/applicationVersion/version`	-
`config`	`sap.ui5/config`	-
`dependencies`	`sap.ui5/depedencies`	Different format, see Dependencies section below
`customizing`	`sap.ui5/extends/extensions`	-
`handleValidation`	`sap.ui5/handleValidation`	-
`includes`	`sap.ui5/resources`	Different format, see Resources section below
`rootView`	`sap.ui5/rootView`	-
`routing`	`sap.ui5/routing`	-

Dependencies

Libraries and components are objects and not arrays. For the descriptor part, we use ui5version instead of minUI5Version.

Metadata

#!js
"dependencies": {
    "ui5version": "1.30.0",
    "libs": [
        "sap.m",
        "sap.ui.unified"
    ],
    "components": [ "sap.app.otherComponent" ]
}

Descriptor

#!js
"dependencies": {
    "minUI5Version": "1.30.0",
    "libs": {
        "sap.m": {},
        "sap.ui.unified": {}
    },
    "components": {
        "sap.app.otherComponent": {}
    }
}

Resources

Includes are renamed to resources and are objects and not an array.

Metadata

#!js
"includes": ["script.js", "style.css"]

Descriptor

#!js
"resources": {
    "js": [
        {
            "uri": "script.js"
        }
    ],
    "css": [
        {
            "uri": "style.css"
        }
    ]
}