On Tue, 16 Mar 2010 12:31:48 -0000, Leonard Richardson <email address hidden> wrote:
> I think the linked branch will resolve this problem. The only exception
> is if there is a named operation that modifies a field you can also
> modify directly, like IBug.status. Of course, this is what mutator
> methods like transitionToStatus do, but we got rid of those methods in
> version 1.0 of the web service, partly for this reason.
>
> Are there any named operations that modify a field you can modify
> directly, but that aren't mutator methods whose _only_ purpose is to
> modify that field? Ie. operations that will still exist in version 1.0
> of the web service.
IBug.setPrivate and IBug.markAsDuplicate still seem to be around on
On Tue, 16 Mar 2010 12:31:48 -0000, Leonard Richardson <email address hidden> wrote:
> I think the linked branch will resolve this problem. The only exception
> is if there is a named operation that modifies a field you can also
> modify directly, like IBug.status. Of course, this is what mutator
> methods like transitionToStatus do, but we got rid of those methods in
> version 1.0 of the web service, partly for this reason.
>
> Are there any named operations that modify a field you can modify
> directly, but that aren't mutator methods whose _only_ purpose is to
> modify that field? Ie. operations that will still exist in version 1.0
> of the web service.
IBug.setPrivate and IBug.markAsDupl icate still seem to be around on
https:/ /edge.launchpad .net/+apidoc/ #bug
does that indicate they should be killed too?
(Plus, I notice that isUserAffected is exported as a POST which
indicates a bug somewhere).
Thanks,
James