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
900 B
900 B
When a task is completed in CLQMS backend, follow these wrap-up steps:
- Run relevant tests (
./vendor/bin/phpunitor targetedphp spark test --filter ...). - If migrations changed, run
php spark migrate/php spark migrate:rollbacklocally and ensure schema updates succeed. - After editing OpenAPI documentation (YAML files or controller mappings), regenerate
public/api-docs.bundled.yamlvianode public/bundle-api-docs.jsand check it into Git. - Confirm code adheres to PSR-12/CodeIgniter conventions (strict types, response format, transactions, guard clauses) before committing.
- Review
git status/diffto ensure only intended files are staged; do not commit.envor other secret files. - For shared logic changes, double-check lookup JSON cache use and response logging.
These steps keep the API consistent, documented, and tested before merging or deploying.