Everything in CAP
Type
Domain: UI & Frontend Bridge
Origin
Signals
More: Apache-2.0
Group by: Capability
Collaborative draft support for CAP Node.js services
The maintainer marks this under active development; public APIs, annotation names and OData contracts may still change.
Event registration app showing OData V4 draft with UI5 and CAP
CAP plugin generating value help for enum fields from an annotation
Parser for annotations in CDS source
Converter from CDS annotations to their OData form
Programmatic API for reading and writing project annotations
OASIS and SAP OData vocabularies with a VocabularyService
Incident Management reference application for CAP
Travel-booking reference app on CAP Node.js and Java backends
Showcase of Fiori elements for OData V4 features on a CAP backend
CodeJam building a bookshop app on the flexible programming model
Exercise solutions for the UX405 course on Fiori elements with CAP
Playback-only SAP Companion (Help4) workarea served from CAP
Not behind a managed approuter: SAP Build Work Zone does not expose the `/$companion/**` routes, so Companion never reaches CAP, and the README names managed approuter and Work Zone as out of scope for v1. Not where help has to be authored in a browser, since the editor, the producer and writes are absent and content lives in files the plugin compiles.
Reader and writer for i18n bundles of UI5 or CAP projects
CAP plugin rendering UI5 views with entity data on the server
On the UI5 path what comes back is an XML view or fragment with the data already substituted, streamed as the entity's media content, rather than an HTML page — the README calls this pre-rendering, and only the Vue path produces markup. The view kept under `srv/` has its UI5 bindings replaced by Handlebars expressions, so it is a second copy of the view, separate from the one the application ships. Version 1.0.8 declares `@sap/cds` `>=8` as its peer dependency, which puts a project on CAP 7 outside its stated range.
UI5 CLI middlewares running inside the CDS server
For a deployed application's UI. The README adds it with `npm add cds-plugin-ui5 -D`, a development dependency of the CDS server, and states nothing about a build or a deployment.
CAP bookshop showing UI5 development with cds-plugin-ui5
