30c4e47304
- handle contact PATCH failures by checking model save result and returning HTTP 400 with the model error message - update ContactDetailModel nested updates to enforce active-detail checks and use model update() with explicit failure propagation - extend contact patch assertions and align test-create variants expectations to status=success for POST responses - refresh composer lock metadata/dependency constraints and include generated docs/data/test files updated during normalization - impact: API contract unchanged except clearer 400 error responses on invalid contact detail updates
14 lines
1.1 KiB
Markdown
14 lines
1.1 KiB
Markdown
Essential commands for CLQMS development (run from repo root on Windows PowerShell):
|
||
|
||
• `composer install` – install PHP dependencies before running CodeIgniter or tests.
|
||
• `npm install` – sync `package-lock.json` for tooling such as API docs bundler.
|
||
• `./vendor/bin/phpunit` – run entire PHPUnit suite (or target files via `--filter`).
|
||
• `php spark test --filter <Class>::<method>` – focused test run when you know the class/method.
|
||
• `php spark migrate` / `php spark migrate:rollback` – apply or roll back database migrations.
|
||
• `php spark serve` – lightweight dev server for the API while developing locally.
|
||
• `node public/bundle-api-docs.js` – regenerate bundled OpenAPI docs whenever the YAML files change.
|
||
• `git status`, `git diff`, `git log --oneline`, `git add <paths>`, `git commit`, `git pull`, `git push` – version control workflow commands.
|
||
• `ls` / `dir` / `Get-ChildItem` – inspect directories in PowerShell; `cd` to move between directories.
|
||
• `type <file>` or `Get-Content` – view file contents when tools are not convenient.
|
||
|
||
Use these commands routinely after code changes, tests, or migrations. |