Person
Tomas Rimkus
Capabilities
Contributes to
Change trackingCAPChange trackingKeeping a readable history of what changed on a record, who changed it and when — as business history rather than database journalling.TypeScript patternsCAPTypeScript patternsHow an application is arranged once it is written in TypeScript — where handlers live, what registers them, and how business logic is kept apart from persistence. Distinct from typing, which is about the model being visible to the compiler; this is about the shape of the code around it.TypingCAPTypingMaking the model visible to the compiler — generated types for entities and events so a rename breaks the build rather than production.
Entries
Group by
EntrySignals
Contributes to
@cap-js/cds-types@cap-js/cds-typesType definitions for the CAP Node.js SDK.sap official, cap
Type definitions for the CAP Node.js SDK
@cap-js/change-tracking@cap-js/change-trackingOut-of-the-box change history for annotated entities.sap official, cap
Change history for annotated CAP entities
@dxfrontier/cds-ts-dispatcher@dxfrontier/cds-ts-dispatcherDecorator-driven handler registration for CAP in TypeScript, where handlers are declared on a class rather than wired up one by one in an init function.independent, cap
Decorator-driven handler registration for CAP in TypeScript
capire/docscapire/docsThe sources of capire itself, in the repository it is built from: the documentation every core_coverage claim in this graph is checked against, so a claim can be dated against a commit.sap official, cap
Sources of capire, the CAP documentation
Details
For your agent
- Ref
actor:hakimio- JSON
- /actors/hakimio.json
- MCP
- Connecting an agent