We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The logging preference is set to 1 by default when creating a project:
$ curl -X POST http://localhost:5000/api/projects -d 'name=machin&id=machin&password=yay&[email protected]' "machine" $ curl -u 'machin:yay' http://localhost:5000/api/projects/machin { "id": "machin", "name": "machin", "contact_email": "[email protected]", "logging_preference": 1, "members": [], "default_currency": "XXX" }
However, if you update the project with PUT and don't specify this field, it gets reset to 0:
$ curl -X PUT -u 'machin:yay' http://localhost:5000/api/projects/machin -d 'name=machinchose&id=machin¤t_password=yay&[email protected]' "UPDATED" $ curl -u 'machin:yay' http://localhost:5000/api/projects/machin { "id": "machin", "name": "machinchose", "contact_email": "[email protected]", "logging_preference": 0, "members": [], "default_currency": "XXX" }
Same thing for the default_currency: if you don't specify it in a PUT, it gets reset to XXX.
XXX
Since older API clients won't know about new optional fields, we should not reset these fields when they are not specified.
The text was updated successfully, but these errors were encountered:
I tried to solve this issue by editing the put function in the ProjectHandler Class.
Sorry, something went wrong.
No branches or pull requests
The logging preference is set to 1 by default when creating a project:
However, if you update the project with PUT and don't specify this field, it gets reset to 0:
Same thing for the default_currency: if you don't specify it in a PUT, it gets reset to
XXX
.Since older API clients won't know about new optional fields, we should not reset these fields when they are not specified.
The text was updated successfully, but these errors were encountered: