- Rules Reference
- async-component-flags
- csp-unsafe-inline-script
- no-ambiguous-event-handler
- no-deprecated-api
- no-deprecated-component
- no-deprecated-control-renderer-declaration
- no-deprecated-library
- no-deprecated-theme
- no-globals
- no-implicit-globals
- no-pseudo-modules
- parsing-error
- autofix-error
- prefer-test-starter
- ui5-class-declaration
- unsupported-api-usage
- no-outdated-manifest-version
- no-removed-manifest-property
- no-legacy-ui5-version-in-manifest
Checks whether a Component is configured for asynchronous loading via the sap.ui.core.IAsyncContentCreation interface in the Component metadata or via async flags in the manifest.json.
Related information
Checks whether inline scripts are used in HTML files in accordance with Content Security Policy (CSP) best practices.
Related information
Checks whether event handlers in XML views/fragments are prefixed by a dot '.' (i.e. represent a controller method) or refer to a local name (via core:require import).
Related information
Checks whether deprecated APIs, features or parameters are used in the project.
Related information
Checks for dependencies to deprecated components in manifest.json.
Related information
Checks whether the renderer of a control is declared correctly.
Checks for dependencies to deprecated libraries in manifest.json and ui5.yaml.
Related information
Checks for usage of deprecated themes in the code and HTML files.
Related information
Checks for the usage of global variables in the code.
Related information
Checks whether:
- modules are accessed via the global library namespace that is exposed by the
librarymodule of a UI5 library odataglobals are used implicitly in bindings without an explicit import of the corresponding modules
Related information
Checks for dependencies to pseudo modules in the code.
Related information
Syntax/parsing errors that appear during the linting process are reported with this rule.
An expected autofix could not be applied. This is likely a UI5 linter internal issue. Please report this using the bug report template: github.com/UI5/linter/issues/
Checks whether test-related files are using the Test Starter concept.
Related information
Checks whether the declaration of UI5 classes is correct. This rule only applies to TypeScript code where built-in ECMAScript classes are used instead of an .extend() call.
Checks whether the UI5 API is used correctly, for example, whether a formatter in a JavaScript/TypeScript binding declaration is of type function.
Legacy-free UI5 requires Manifest Version 2. This test checks the _version property in manifest.json.
Manifest Version 2 lacks several properties of earlier versions, which do not match anymore to the new schema. They must be omitted.
Checks the sap.ui5/dependencies/minUI5Version property in manifest.json for legacy UI5 versions, which must not be used.
This rule ensures that projects specify a minimum UI5 version that supports modern development practices. As of OpenUI5/SAPUI5 1.136, the new Manifest Version 2 is supported, which provides enhanced capabilities for UI5 applications.
Related information