On Mon, Jul 15, 2013 at 8:34 PM, Lucas Holmquist <lholmqui(a)redhat.com
<mailto:lholmqui@redhat.com>> wrote:
> here's a scenario.
>
> A user creates an "Application" then adds a new "iOS
Variant"
> to it.
>
> they decide they need to rename this Variant since they
> didn't name it very well.
>
> There is currently no way of renaming/ updating the
> description of this variant without re-sending the
> Certificate/pass phrase. this would be the same for Android
> and Simple Push, just substitute google key and channels
>
>
> Is this really a problem ? Since before an update I assume you do
> a GET which will contain the Certificate/pass phrase, and then
> just doing an update passing the whole object again ... I might
> be missing sometyhing obvious here.
i have all the info, was hoping to avoid having to resend the
certificate/other stuff again.
Ok I see, with the current model that is not really possible (saying
trivially) . We could extract all this info (cert/pass whatever) into
a different model/class and just having a 1-1 relation making the
update on the variant more simple. But I would like to have Matzew
feedback on this.
I think the same goes for renaming the Application construct?
Though it just contains an extra "description" field, so it may not be
worth it...
Would like to hear Matthew ideas on this as well from an API design
point of view. :)
Hylke