Closed richardpawson closed 10 years ago
Addressed in RO spec 1.1, see for example https://github.com/danhaywood/restfulobjects-spec/commit/ed2e79fdc177b1f560ef904a0a4ac795792fcbd5
added into RO spec 1.1, eg https://github.com/danhaywood/restfulobjects-spec/commit/90f7b4e4fbe49564bcf3b3cc356ac9a99fa9f7a3
On 29 July 2013 08:39, Richard Pawson notifications@github.com wrote:
[copied from an email originally from Stef Cascarini]
My scenario is to edit an object and 'PUT' the changes. All OK so I get back the updated object as per 14.2.2. I'd like to just use this updated object but I can't because it has no self link.
Since other fields may have changed (eg title) I either need to copy all the fields across from the updated object or copy the self link across from the old object. Either is ugly. I can't really see any reason for the missing self link - the object has been successfully updated so what's the harm in having a link ? Perhaps it could be reconsidered in v.next of the spec ?
— Reply to this email directly or view it on GitHubhttps://github.com/danhaywood/restfulobjects-spec/issues/17 .
[copied from an email originally from Stef Cascarini]
My scenario is to edit an object and 'PUT' the changes. All OK so I get back the updated object as per 14.2.2. I'd like to just use this updated object but I can't because it has no self link.
Since other fields may have changed (eg title) I either need to copy all the fields across from the updated object or copy the self link across from the old object. Either is ugly. I can't really see any reason for the missing self link - the object has been successfully updated so what's the harm in having a link ? Perhaps it could be reconsidered in v.next of the spec ?