You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Laminas\ApiTools\Rest\RestController::delete($id)
If I return own Laminas\Http\Response on line 443 as $result, the event 'delete.post' won't be triggered.
Scenario
Resource deletion leads to change of other resources and client must be notified about it. So we return 200 with response body. But if other modules listen for 'delete.post' and perform extra actions - they won't be notified about resource deletion.
Suggestion
Check if $result is instance of Laminas\Http\Response separately from ApiProblem / ApiProblemResponse and trigger 'delete.post' before returning it.
The text was updated successfully, but these errors were encountered:
RFC
Laminas\ApiTools\Rest\RestController::delete($id)
If I return own Laminas\Http\Response on line 443 as $result, the event 'delete.post' won't be triggered.
Scenario
Resource deletion leads to change of other resources and client must be notified about it. So we return 200 with response body. But if other modules listen for 'delete.post' and perform extra actions - they won't be notified about resource deletion.
Suggestion
Check if $result is instance of Laminas\Http\Response separately from ApiProblem / ApiProblemResponse and trigger 'delete.post' before returning it.
The text was updated successfully, but these errors were encountered: