refactor: standardise error response format across API controllers #65
No reviewers
Labels
No labels
P1
P2
P3
PHP
agent-ready
bug
clotho
discovery
docs
epic
refactor
review
security
testing
athena
athena-gemini
audit
clotho
clotho-gemini
codex
darbs-claude
security
wiki
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: core/php-tenant#65
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "feat/standardise-error-responses"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
HasStandardApiResponsestrait inConcerns/with consistent error format:{"success": false, "error": "Human-readable message", "code": "MACHINE_READABLE_CODE"}EntitlementApiController,EntitlementWebhookController, andWorkspaceControllerresponse()->json()error/success calls with trait methodsEntitlementApiTestassertions to match the newcodefieldFixes #20
Test plan
composer testto verify all existing tests pass with updated assertionssuccess,error, andcodefieldssuccess: trueAdd HasStandardApiResponses trait with consistent error format: {"success": false, "error": "Human-readable message", "code": "MACHINE_READABLE_CODE"} Applied to EntitlementApiController, EntitlementWebhookController, and WorkspaceController. Updated tests to assert the new format. Fixes #20 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.