Felix KemmlerandClaude Sonnet 5
dfeb37cf33
Docker-Images bauen und veröffentlichen / build (, omsorgCore/Dockerfile, omsorgcore) (push) Successful in 17s
Docker-Images bauen und veröffentlichen / build (, omsorgWeb/Dockerfile, omsorgweb) (push) Successful in 6s
Docker-Images bauen und veröffentlichen / build (, omsorgapp/Dockerfile, omsorgapp) (push) Successful in 17s
Adds the Assignment core object (Order x Employee, date range) with full CRUD, soft-delete/trash integration, and generated API clients. Layers FR-EM-3 conflict checks onto assignment creation: qualification, absence/availability, working-hours approximation, cross-order overlap, and active-contract coverage. Each check's severity (Warning vs. Error) is configurable at runtime via a new AssignmentValidationSettings singleton and admin settings panel, instead of being hardcoded - lets the business tune strictness per check without a redeploy. Adds a live GET /api/assignments/check endpoint so the create-assignment dialog can preview conflicts as the user picks employee/dates, before they hit save, rather than only finding out after submitting. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Omsorg Business Controls Pro – Release 0.1.1 Foundation
Stabile lokale Electron/React-Basis ohne native SQLite-Abhängigkeit.
Warum 0.1.1?
Release 0.1.0 nutzte better-sqlite3. Auf macOS/Electron kann dieses native Modul Versionsprobleme verursachen.
Release 0.1.1 speichert Daten zuerst in einer lokalen JSON-Datenbank im Benutzerordner.
Start
cd ~/Desktop/omsorg-business-controls-pro-release-0.1.1
npm install
npm run dev
Lokale Daten
Die App legt Ordner unter ~/Documents/Omsorg Business Controls Pro an:
- database/omsorg-local-db.json
- documents/employees
- documents/customers
- backups
Nächster Sprint
SQLite wird später sauber über eine entkoppelte Persistenzschicht eingebaut.