onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
PersonSAP

Christian Georgi

1maintains47contributes to
GitHub@chgeolast push

Capabilities23

Provides 1
OpenAPICAPOpenAPIcapabilityHanding a description of the service to clients and tools — an API portal, a code generator, a partner who wants a contract before they write anything.
Contributes to 22
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.AttachmentsCAPUI5AttachmentscapabilityStoring a file somebody uploaded next to the record it belongs to, and getting it back out — where the bytes actually live, who may read them, and what the UI shows while they are being scanned.Audit loggingCAPAudit loggingcapabilityRecording who touched personal or sensitive data, in a form an auditor accepts, without hand-writing it in every handler. It is often confused with application logging, which records what the code did rather than who accessed what.Change trackingCAPChange trackingcapabilityKeeping a readable history of what changed on a record, who changed it and when — as business history rather than database journalling.CI/CD pipelinesCAPCI/CD pipelinescapabilityA pipeline that builds, tests and delivers an application each time its source repository changes, with a build log that shows which step failed. [Deployment](capability:deployment) describes getting the build onto its target runtime.Database connectorsCAPDatabase connectorscapabilityConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to [schema evolution](capability:schema-evolution).DebuggingCAPDebuggingcapabilitySeeing what running code did between an input arriving and a result coming out: which code ran, what the values were at each point, and why a value ended up as it did.DeploymentCAPDeploymentcapabilityGetting an application onto a runtime and keeping it there: build descriptors, deployment topology, service bindings and lifecycle operations. The target runtime determines how the application is packaged and configured.Document outputCAPDocument outputcapabilityProducing a document a person receives — a printed form, a generated PDF, a filled template — and getting it to a printer or a queue rather than returning it as a payload.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.Editor supportCAPUI5Editor supportcapabilityWorking in source code with the editor helping rather than treating it as text — completion, go-to-definition, inline errors, refactoring and preview.Event MeshCAPEvent MeshcapabilityEmitting and consuming business events across systems through brokers, including subscriptions and mapping application events to broker topics. Work that must survive a request, including deferred processing and retries, belongs to [async processing](capability:async-processing).GraphQLCAPGraphQLcapabilityServing the same model over GraphQL instead of OData — one endpoint, the client naming the fields it wants, for consumers who expect that shape rather than an OData one.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.LoggingCAPUI5LoggingcapabilitySeeing what a running service did, in a form something can read afterwards — levels, a formatter that suits a laptop and one that suits a log service.Metadata publishingCAPMetadata publishingcapabilityDescribing a service to something other than a human — service metadata for clients, and machine-readable descriptions for registries and discovery.NotificationsCAPNotificationscapabilityTelling a person something happened when they are not looking at the screen — a notification in the launchpad, an email, a message somewhere they already are.ODataCAPODatacapabilityExposing data and operations through OData, including the service model, metadata and protocol versions clients require. Version differences affect which clients can consume a service and which query features they can use.TelemetryCAPTelemetrycapabilitySeeing what a running service did — traces across handlers and database calls, metrics, and correlation that survives an async boundary.TestingCAPTestingcapabilityProving the service still does what it did — against the model and the handlers, without a deployed system and without a database somebody has to keep clean.TypingCAPTypingcapabilityMaking the model visible to the compiler — generated types for entities and events so a rename breaks the build rather than production.

Entries48

Group by48 of 48 entries
EntrySignals
Maintains1
cds-swagger-ui-expressv0.11.0
none

Swagger UI for a CAP service's OpenAPI definition

Contributes to47
@cap-js-community/business-metricsv1.0.0
none

Business-level metrics from CDS annotations via @cap-js/telemetry

@cap-js-community/odata-v2-adapterv1.16.2
none

Exposes a CAP service as OData V2

@cap-js/advanced-event-meshv1.1.0
none

CAP integration with SAP Integration Suite advanced event mesh

@cap-js/asyncapiv1.1.0
none

Exports AsyncAPI documents for a CAP service's events

@cap-js/attachmentsv4.0.0
none

CAP Node.js attachments with database, S3, Azure or GCP storage

@cap-js/audit-loggingv1.3.0
none

CAP integration with the SAP Audit Log service

@cap-js/cap-operator-pluginv0.20.0
none

Generates Helm charts for the CAP Operator on Kubernetes

@cap-js/cds-dbsv1.3.1
none

Monorepo of CAP's SQL database services

@cap-js/cds-testv1.0.2
none

Test support for CAP Node.js: server start, HTTP client, assertions

@cap-js/cds-typerv0.41.1
none

Generates TypeScript types from a CDS model

@cap-js/cds-typesv0.20.0
none

Type definitions for the CAP Node.js SDK

@cap-js/change-trackingv2.2.3
none

Change history for annotated CAP entities

@cap-js/consolev1.0.2
none

Connects a running CAP application to the CAP console

@cap-js/data-inspectorv2.0.1
none

Inspects database entities and contents at CAP service level

@cap-js/db-servicev3.1.2
none

Base service shared by CAP's SQLite, PostgreSQL and HANA services

@cap-js/event-brokerv0.3.1
none

Consumes events from SAP Cloud Application Event Hub in CAP

@cap-js/graphqlv0.14.0
none

GraphQL protocol adapter generated from the CDS model

@cap-js/hanav3.1.2
none

SAP HANA database service for CAP

@cap-js/mcp-serverv0.0.8
Functional boundary

MCP server for CAP development: model and docs search

@cap-js/notificationsv1.1.1
none

Business notifications from CAP to SAP Build WorkZone

@cap-js/openapiv1.7.0
none

Generates OpenAPI documents from a CDS service

@cap-js/ordv1.10.2
none

Generates Open Resource Discovery documents from a CAP model

@cap-js/postgresv3.1.2
none

PostgreSQL database service for CAP

@cap-js/printv0.2.1
none

Prints documents held in CAP entities through SAP Print service

@cap-js/sdmv1.11.0
Functional boundary

CAP attachments stored in an SAP Document Management repository

@cap-js/sqlitev3.1.2
none

SQLite database service for CAP, in memory during development

@capire/data-viewer
Functional boundary

Sample CAP plugin adding a generic data browser

capire/bookshop
none

CAP's getting-started bookshop sample

capire/bookstore
none

Composite CAP app from separately deployed services

capire/docs
none

Sources of capire, the CAP documentation

capire/incidents-app
none

Incident Management reference application for CAP

cds-cucumber
none

Gherkin scenarios driving a running CAP service

cds-intellij
none

SAP CDS language support for IntelliJ IDEA

cds-plugin-ui5v0.17.4
Functional boundary

UI5 CLI middlewares running inside the CDS server

cds-textmate-grammar
Functional boundary

TextMate grammar for the CDS language

cf-setup
none

GitHub Action setting up the Cloud Foundry CLI

com.sap.cds:sdm
Functional boundary

CAP Java plugin for attachments in SAP Document Management

commonv0.2.5
none

Sample CAP plugin extending @sap/cds/common with reuse data

orders
Functional boundary

Sample CAP reuse service for orders, with a Fiori UI

reviewsv0.1.0
Functional boundary

Sample CAP reuse service for reviews, with a Fiori UI

SAP-samples/cap-sflight
none

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

SAP-samples/cloud-cap-samples-java
none

Bookshop app demonstrating the CAP Java SDK end to end

SAP-samples/fiori-elements-v4-cap-advanced
none

Exercise solutions for the UX405 course on Fiori elements with CAP

shared-db
Functional boundary

CAP sample sharing one domain model and database across apps

vite-plugin-cdsv0.3.6
none

Serves a Vite app through cds watch and imports .cds files

xflights
none

CAP reuse package serving Airlines, Airports and Flights data

xtravels
none

CAP travel-booking app built on xflights master data

Details

History2
  • cds-swagger-ui-expressdescription.one_line → Serves a CAP service's OpenAPI definition as a browsable Swagger UI, which is the page @cap-js/openapi's document does not come with.Placement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
  • First entry seenDiscovered via npm registry, The discovery pass.
For your agent
Ref
actor:chgeo
JSON
/actors/chgeo.json
MCP
Connecting an agent