Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIX: PUT /thirdparties/{id} and PUT /contacts/{id} should throw exception if update returns < 0 + other issues #29596

Conversation

atm-florianm
Copy link
Contributor

FIX #29594

Now I really think setting the notrigger param to 1 when calling Contact::update was just a copy/paste mistake (because it makes sense for the 3rd param of Societe::update to be 1 since this parameter is call_trigger and does the opposite of notrigger).

I also include in this PR a missing 500 throw when the endpoint fails to update the object (both Contact and Societe) + some minor PHPDoc inaccuracies.

@eldy I know you usually don't want to change REST API behaviour in released versions of Dolibarr even when the behaviour is arguably wrong, so if you feel that this change is significant enough, feel free to change the target branch to develop.

…tion if update returns < 0

+ FIX some PHPDoc (types and throws)
+ FIX issue Dolibarr#29594: trigger should be called on contact update by API
@eldy eldy merged commit cf6cbaf into Dolibarr:17.0 May 3, 2024
3 checks passed
@atm-florianm atm-florianm deleted the FIX_17_restapi_put_contact_missing_throw_on_error branch May 3, 2024 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants