API named operations that modify an object don't always return the modified object
Bug #369293 reported by
Deryck Hodge
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
lazr.restful |
Triaged
|
Low
|
Unassigned | ||
lazr.restfulclient |
Triaged
|
Low
|
Unassigned |
Bug Description
I ran into an issue with the JavaScript client where a named operation that modified a bugtask object didn't return the modified object; then subsequent calls to lp_save would generate a 412 Precondition failed error (like bug #336866).
In talking about this with leonardr on IRC, it seems named operations really should return the modified object with a 209 response code. The Python and JavaScript clients should handle this correctly then.
affects: | launchpad → lazr.restful |
tags: | added: tech-debt |
Changed in lazr.restful: | |
status: | New → Triaged |
Changed in lazr.restfulclient: | |
status: | New → Triaged |
Changed in lazr.restful: | |
importance: | Undecided → Medium |
Changed in lazr.restfulclient: | |
importance: | Undecided → Medium |
Changed in launchpad: | |
importance: | Undecided → Medium |
status: | New → Triaged |
summary: |
- API named operations that modify an object should return the modified - object + API named operations that modify an object don't always return the + modified object |
Changed in lazr.restfulclient: | |
importance: | High → Low |
Changed in lazr.restful: | |
importance: | High → Low |
Changed in launchpad: | |
importance: | High → Low |
To post a comment you must log in.
How would we tell a-priori whether a given named operation mutates the object or not?