@sap/ux-cds-odata-language-server-extension
Adds the OData annotation features to @sap/vscode-cds@sap/vscode-cdsSAP CDS language support for Visual Studio Code and Business Application Studio, published as an npm library.sap official, cap, the CDS plug-in for Visual Studio Code: completion, micro-snippets, diagnostics, vocabulary documentation, Go to Definition and an i18n check inside a .cds file.
Writing OData annotations in CDS means knowing which vocabulary terms exist, which records and properties each one allows, and what the values may be. This extension moves that into @sap/vscode-cds@sap/vscode-cdsSAP CDS language support for Visual Studio Code and Business Application Studio, published as an npm library.sap official, cap, the CDS plug-in for Visual Studio Code: suggestion lists built from the service metadata and the OData vocabularies and cut down to what the specification allows, micro-snippets for repeating blocks such as annotation aliases, terms and records, diagnostics that validate annotations against the project metadata and the vocabularies, documentation on a term saying whether it is experimental, deprecated or mandatory, Go to Definition and Peek Definition for a referenced annotation, and a warning where a translatable value is hard-coded instead of written as an i18n reference. It states its own boundary: completion for path values is offered only for files referenced through the using directive and for annotations applied to entities exposed from the same service, and CDS Common annotations, annotations on complex elements, annotations embedded in entity definitions and annotations on parameters of parameterized entities are outside its scope.
Facts
Where it sits
Who is behind it
In the atlas: maintains 137, wrote 14@SAPmaintainer
What it declares
Every artifact
- Type
- IDE extension
- Origin
- By SAP
- Runtime
- Node.js
As an IDE extension
- Installs into
- VS Code
- Distributed through
- does not say
Connections
Editor help with source: completion, navigation, errors, refactoring
Describing a service so a Fiori client renders it without UI code
CDS language support for VS Code and Business Application Studio
Download
Install
npm add @sap/ux-cds-odata-language-server-extensionDerived from the package name. No recipe recorded; the README has the configuration.
README
quoted from @sap/ux-cds-odata-language-server-extension@1.33.0, read@sap/ux-cds-odata-language-server-extension
The SAP Fiori Tools - CDS OData Language Server enhances the functionality of SAP Cloud Platform core data services plug-in for Visual Studio Code with the features assisting you to define OData annotations in .cds files serving Fiori UIs.
History
Removed 1, Features 3
Changed 1, Fixes 2
Changed 2
Changed 2
Features 2
Features 1
Features 1
Fixes 3
Fixes 1
Fixes 1
Features 2, Changed 1
Changed 1, Fixes 1
Changed 1
Features 1, Changed 1
Features 1, Changed 1
Features 2
Changed 1
Features 3
Features 7, Changed 2
Features 4
Changed 1, Fixes 4
Features 1, Changed 1
Fixes 1
Features 2, Changed 1, Fixes 5
Features 3, Fixes 1
Features 6
Others providing
- cds-eclipse-plugincds-eclipse-pluginEclipse plugin for the CDS language.independent, capEclipse plugin for the CDS language
- SAP Build CodeSAP Build CodeSAP's development environment on BTP for SAPUI5, SAP Fiori, mobile and CAP applications that run on the SAP BTP, Cloud Foundry Runtime, in which Joule generates models, services, logic, tests and apps.sap official, btpDevelopment environment on BTP for UI5, Fiori, mobile and CAP
- cds-intellijcds-intellijSAP CDS language support for IntelliJ IDEA.sap official, capSAP CDS language support for IntelliJ IDEA
- @sap/cds-lsp@sap/cds-lspLanguage server for CDS — the engine behind completion, navigation and inline errors in every supported editor.sap official, capLanguage server for CDS
- cds-textmate-grammarcds-textmate-grammarThe TextMate grammar for the CDS language, which highlights .cds files where the CDS language server does not run, most visibly in GitHub's own file viewer through Linguist.sap official, capTextMate grammar for the CDS language
- @sap/vscode-cds@sap/vscode-cdsSAP CDS language support for Visual Studio Code and Business Application Studio, published as an npm library.sap official, capCDS language support for VS Code and Business Application Studio
- @saptools/hana-lens@saptools/hana-lensCompiles every CAP package in a workspace into one minified CSN cache, so "where is this entity and what columns does it have" is a query rather than a monorepo load.independent, capWorkspace-wide CSN cache for querying CAP entities and columns
- zed-cds-extensionzed-cds-extensionCDS language support for the Zed editor, wiring the CDS language server into it.independent, capCDS language support for the Zed editor
- com.sap.cds:cds-services-bomcom.sap.cds:cds-services-bomThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, capMaven bill of materials pinning CAP Java module versions
- urp-vocaburp-vocabA CDS vocabulary for User-Rendered Patterns, with @urp.display annotations describing views, card templates, layouts and sections on an entity, consumed by the author's own matching renderer.independent, capCDS vocabulary for User-Rendered Patterns display annotations
- @mpah/enum-value-help@mpah/enum-value-helpA CAP plugin that generates value help for enum fields from an @enumValueHelp annotation, serving the enum's values from one generated entity instead of hand-written OData annotations.independent, capCAP plugin generating value help for enum fields from an annotation
- @sap/cds-fiori@sap/cds-fioriFiori draft handling and UI-facing behaviour for CAP services.sap official, capFiori draft handling and UI-facing behaviour for CAP services
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtime
- @sap/generator-fiori@sap/generator-fioriThe single entry point for generating a Fiori application — the user picks a template and the generator produces the project around it.sap official, capEntry point for generating a Fiori application from a template
- @sap-ux/cds-annotation-parser@sap-ux/cds-annotation-parserParses annotations out of CDS source, so tooling can read what a model says about its UI without compiling it.sap official, capParser for annotations in CDS source
- @sap/ux-cds-compiler-facade@sap/ux-cds-compiler-facadeWraps the CAP CDS compiler behind one set of APIs for annotation handling, so tooling reads a model without tracking which compiler version is installed.sap official, capWrapper around the CDS compiler for annotation handling
- @sap-ux/cds-odata-annotation-converter@sap-ux/cds-odata-annotation-converterConverts CDS annotations into their OData form, which is the translation Fiori tooling needs to reason about a service the way a client sees it.sap official, capConverter from CDS annotations to their OData form
- @sap-ux/fiori-annotation-api@sap-ux/fiori-annotation-apiThe programmatic API Fiori tooling uses to read and write annotations on a project, rather than editing the files as text.sap official, capProgrammatic API for reading and writing project annotations
- @sap-ux/odata-vocabularies@sap-ux/odata-vocabulariesCarries the OASIS and SAP OData vocabularies as a package, with a VocabularyService for asking which terms exist, where they apply and what their types and properties are.sap official, ui5OASIS and SAP OData vocabularies with a VocabularyService
- cap-js-geoloc-plugincap-js-geoloc-pluginA CAP plugin for geocoding, address correction and route calculation, driven by three annotations on the model, with the geocoder and router chosen in configuration from providers such as OSRM and Nominatim.independent, capAnnotation-driven geocoding, address correction and routing for CAP
- cap-user-infocap-user-infoResolves the createdBy and modifiedBy of a managed entity to a stored user record of email, given name and family name, and renders the two fields as links with a quickview.independent, capUser details and quickview links for createdBy and modifiedBy
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
History in the atlas
- First seen.
For your agent
- Ref
artifact:sap-ux-cds-odata-language-server-extension- JSON
- /artifacts/sap-ux-cds-odata-language-server-extension.json
- MCP
- Connecting an agent