Editor support
In a UI5 project the editor has to know the framework's control metadata: which aggregations a control takes, which properties and events it has, and which controller method an XML event handler names. SAP's UI5 Language Assistant reads that metadata for the XML view; the controller code beside it is the other half of the same project.
Overview
SAP publishes UI5 Language Assistant for VS Code, driven by SAPUI5 metadata it downloads lazily. In XML views and fragments it completes classes, aggregations, properties, events and enum values filtered by the parent aggregation's type, validates unknown tags and attributes, duplicate IDs, aggregation cardinality and binding info, shows hover tooltips, navigates from a view to the controller files it references and formats views and fragments with prettier; in manifest.json it completes and validates.
Not covered: At XML views and the manifest, for SAP's own controls: its README states that custom controls are not supported and get no completion, its validations and their severity are fixed and cannot be configured, and it lists no completion inside controller JavaScript or TypeScript.
ui5pluginui5pluginThe SAPUI5 Extension for Visual Studio Code: completion, definitions, CodeLens, diagnostics, code actions, hover and an XML formatter for UI5 views, controllers and manifest.json.independent, ui5, the SAPUI5 Extension for VS Code, covers the controller side too: completion in XML views, JavaScript, TypeScript and manifest.json, definitions from an XML event handler to its controller method, CodeLens, a rename provider and i18n export, with diagnostics from ui5plugin-linterui5plugin-linterA command-line linter for UI5 projects, run as ui5linter, that checks JavaScript and TypeScript classes, XML views and fragments, and i18n properties files.independent, ui5.
Artifacts
Details
Coverage
For your agent
- Ref
capability:editor-support- JSON
- /capabilities/editor-support.json
- MCP
- Connecting an agent