OpenAPI: non-compliance with specification and other stranger things [draft]

[trojikman]

1. Different behavior between curl and Bravado I have noticed the difference between sending PUT requests to API between curl and python library Bravado, there will be different behavior because of specification flaw. And because bravado works according to specification it imposes a restriction on freedom of action and completeness of the user experience.

Example: If we try to create new record via curl we can fill in the x2many field by passing new record (like [0, 0, values]) but in case of using Bravado we can only pass record id. What to do: In this case, I'm not entirely sure which option is more correct but I think that everything should work the same in both cases.

2. Response codes don't meet specification (from #152) Here are some examples:

1. Request from allowed user without rights to read fields in odoo (Joel Willis if you use demo data) will get you an internal error.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[trojikman]

via Hubstaff User: Denis Mudarisov

Project: sync-addons - https://app.hubstaff.com/projects/1618283 Date Range: 08/17/21 - 08/17/21 Work session total: 0:10:49 Billable: Yes

Grand total: 0:10:49