ui5-cap-todo
A todo application with a CAP backend and a SAPUI5 frontend, both in TypeScript, connected over OData V4 in one pnpm workspace, with projects and their todos in a master-detail FlexibleColumnLayout.
Projects and their todos in a master-detail FlexibleColumnLayout, with deadlines, priorities, inline editing, a status filter, sorting and grouping. On the CAP side it has a bound action completeAll, per-project progress computed as virtual elements, and a validation that rejects past deadlines with localised messages; the UI5 side binds an OData V4 model and transpiles with ui5-tooling-transpile. Data is seeded from CSV into a SQLite file, or into memory with a separate start script. German and English texts cover both halves.
Facts
Where it sits
Who is behind it
In the atlas: maintains 8, contributes to 10, wrote 1@mariokernichmaintainer
Before choosing this
Signals
LicenceNo licenseNeither the package manifest nor the repository tree declares a licence
Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.
What it declares
Every artifact
- Type
- Sample
- Origin
- Independently maintained
- Runtime
- Node.js
As a sample
- Type declarations
- declared
- Form
- A reference application
Connections
Whole applications to read rather than snippets to copy
Download
README
quoted from mariokernich/ui5-cap-todo, readTodo Fullstack App — CAP + UI5 (TypeScript)
Best-practice example of a fullstack app with SAP CAP (Node.js/TypeScript) as backend and SAPUI5 (TypeScript) as frontend, connected via OData V4.

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:mariokernich-ui5-cap-todo- JSON
- /artifacts/mariokernich-ui5-cap-todo.json
- MCP
- Connecting an agent