PersonSAP

Peter Muessig

GitHub@petermuessiglast push

Capabilities8

Provides 1
Integrated frontend dev serverCAPUI5Integrated frontend dev servercapabilityServing a frontend and its backend services together during development, so they can be reached through one local origin. Serving prebuilt files and integrating a frontend toolchain that assembles resources on demand are different requirements.
Demonstrates 2
Integrated frontend dev serverCAPUI5Integrated frontend dev servercapabilityServing a frontend and its backend services together during development, so they can be reached through one local origin. Serving prebuilt files and integrating a frontend toolchain that assembles resources on demand are different requirements.Local developmentCAPLocal developmentcapabilityRunning the whole stack on a laptop against real bindings — the service, the UI and the routing in front of it — without deploying to see a change.
Contributes to 6
Agent access to your codeCAPUI5Agent access to your codecapabilityLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from [MCP servers](capability:mcp-servers), which is a protocol adapter on your own running service, and from [agent guidance](capability:agent-guidance), which is knowledge handed over as files rather than read from the thing itself.DocumentationCAPUI5DocumentationcapabilityFinding the answer in what has already been written, and writing it where it has not — first-party documentation made searchable by something other than a person scrolling it, including by an agent, and a document of custom code produced from the code itself.Fiori annotationsCAPUI5Fiori annotationscapabilityDescribing a service so a Fiori client can render it without hand-written UI code — titles, value helps, hierarchies and visibility expressed as model annotations rather than screen logic.GeneratorsCAPUI5GeneratorscapabilityGetting from nothing to a project that runs, and from a project that runs to one that has the piece you just decided you need. Two different moments: the first is a one-time decision about layout, the second recurs for the life of the project.LintingCAPUI5LintingcapabilityCatching in the editor what would otherwise be caught at deploy time, or not at all — problems in source code and models and in the project's configuration, found by rules rather than by review.TelemetryCAPTelemetrycapabilitySeeing what a running service did — traces across handlers and database calls, metrics, and correlation that survives an async boundary.

Entries15

Group by15 of 15 entries
EntrySignals
Maintains1
cds-plugin-ui5v0.17.4
Functional boundary

UI5 CLI middlewares running inside the CDS server

Maintains: samples, sketches and references3
approuterv0.0.1-security
none

Showcase for dev-approuter in front of two UI5 apps

cds-bookshop
none

CAP bookshop showing UI5 development with cds-plugin-ui5

ui5-bookshop-viewer
none

UI5 app consuming the cds-bookshop server via ui5-middleware-cap

Contributes to11
@sap-ux/cds-annotation-parserv1.1.1
none

Parser for annotations in CDS source

@sap-ux/cds-odata-annotation-converterv1.1.1
none

Converter from CDS annotations to their OData form

@sap-ux/eslint-plugin-fiori-toolsv10.17.3
none

ESLint rules for projects the Fiori tools generators produce

@sap-ux/fiori-annotation-apiv1.1.4
none

Programmatic API for reading and writing project annotations

@sap-ux/fiori-docs-embeddingsv1.2.8
none

Fiori documentation indexed as embeddings

@sap-ux/fiori-generator-sharedv1.2.23
none

Shared functions and types of the Fiori generators

@sap-ux/fiori-mcp-serverv1.15.15
none

MCP server for creating and editing Fiori applications

@sap-ux/telemetryv2.0.12
none

Library for sending usage telemetry data

dev-approuterv0.7.2
none

Dev-time wrapper for the SAP Application Router

SAP-samples/cap-sflight
none

Travel-booking reference app on CAP Node.js and Java backends

SAP-samples/ui5-cap-event-app
none

Event registration app showing OData V4 draft with UI5 and CAP

Details

History8
  • cds-plugin-ui5description.what_it_solves → A CDS server serves the files under `app/`. A UI5 CLI project is not a folder of files ready to serve: its framework resources are resolved and its middlewares configured by `ui5.yaml`, and until something runs that chain the project needs a server of its own. This plugin runs it inside the CDS server, for a project in `app/`, in the folder `cds.env.folders.app` names, or added as a dependency of the CDS server. Each project is mounted under a path derived from the `metadata/name` of its `ui5.yaml`, overridable in the `ui5.yaml` itself, in the CDS server's `package.json` or through `CDS_PLUGIN_UI5_MODULES`. In a project it is one development dependency and an existing `ui5.yaml`, on [@sap/cds](artifact:sap-cds) 6.8.2 or higher.The paragraph claimed live transpiling, which the README does not mention, and said nothing about the two facts a reader needs: where a project has to sit and what it has to be. Rewritten from the README's own sentences. capire's plugin list is where the transpiling claim comes from, and it is quoted on the capability instead of asserted here.
  • cds-plugin-ui5provides → capability:ui5-dev-server, with what_it_does, sources and two facet valuesThe edge was a bare ref, so the page said the plugin answered the capability and nothing about how. The README supplies both facet answers and the mount-path behaviour.
  • cds-plugin-ui5compat.cds_range → >=6.8.2The README states the floor: "The plugin requires [`@sap/cds`](https://www.npmjs.com/package/@sap/cds) `>=6.8.2`."
  • cds-plugin-ui5flavors → nodeThe README's opening sentence says it is a cds-plugin for the node runtime, so the flavor is stated rather than derived from the artifact type.
  • cds-plugin-ui5identity.license, source_available → Apache-2.0, trueRead from the package's own README licence section, as its siblings in the same repository already record.
  • cds-plugin-ui5contributors → actor:petermuessigTwo actor files carried the same GitHub login. peter-m-ssig was keyed on a slugified display name — the umlaut in "Peter Müssig" drops out of the slug, so it looked nothing like the crawled petermuessig and nobody spotted the double. Merged onto the login, which is the identity the crawl matches on.
  • cds-plugin-ui5origin_ring → community-orgui5-community is the UI5 ecosystem's community org, the counterpart of cap-js-community. It was absent from the owner table because that table only knew CAP, so this fell through to independent. Found by probing UI5.
  • First entry seenDiscovered via Added by hand, npm registry, capire · plugins.
For your agent