Skip to content

Latest commit

 

History

History
27 lines (13 loc) · 1.72 KB

project-validation-6f3c737.md

File metadata and controls

27 lines (13 loc) · 1.72 KB

Project Validation

When the project is generated, you can validate it by opening the Command Palette ([CMD/CTRL] + [Shift] + [P] ) and executing the Fiori: Validate Project command. Use a quick pick selection to select a project for validation from the multiple projects in the workspace.

The validation comprises of the following steps:

  • project

    The project step checks that files such as package.json, manifest.json, and ui5.yaml exist and their mandatory fields are filled.

  • annotation

    The annotation step validates the project annotation files using the same modules as the XML annotation language server extension.

  • specification

    The specification step validates manifest.json and files in the changes folder. The @sap/ux-specificationmodule is used to import the project and provide invalid configuration error messages.

  • eslint

    The eslint step checks if eslint is installed as a dependency. If it is, the project validation runs the eslint check based on the project's configuration and the rules defined in the eslint-plugin-fiori-custom. You can enable eslint support for a new project by selecting the appropriate options in the Advanced Options of the SAP Fiori application generator, as described in the Additional Configuration section.

After all validation steps are executed, a report is generated and displayed as a Markdown (.md) file and in the Problems tab of Visual Studio Code (VS Code) or SAP Business Application Studio.