Re: v3 cc api style guide feedback requested


James Bayer
 

the example used for actions uses the v2 api instead of v3:
https://github.com/cloudfoundry/cc-api-v3-style-guide#example-4

i like the idea of a unique error code. ideally the CAPI team maintains
public documentation of an error code dictionary
https://github.com/cloudfoundry/cc-api-v3-style-guide#issues-with-v2-error-format

the async proposal seems like a big improvement.

On Wed, Sep 2, 2015 at 8:53 AM, James Bayer <jbayer(a)pivotal.io> wrote:

the collections example [1] does not actually include the required
*resources* field

[1] https://github.com/cloudfoundry/cc-api-v3-style-guide#example-2


On Wed, Sep 2, 2015 at 8:16 AM, James Bayer <jbayer(a)pivotal.io> wrote:

should the PUT example that updates the app name and space guid actually
be a PATCH since it updates the resource?
https://github.com/cloudfoundry/cc-api-v3-style-guide#put


On Wed, Sep 2, 2015 at 1:40 AM, Dieu Cao <dcao(a)pivotal.io> wrote:

Hi All,

The CAPI team has created a style guide for v3 of the cloud controller
api and would like to share this again with the wider cf community for
feedback after initial review within the team. [1]
Issues/PRs are welcome and appreciated!

Thanks,
Dieu
CF CAPI PM

[1] https://github.com/cloudfoundry/cc-api-v3-style-guide


--
Thank you,

James Bayer


--
Thank you,

James Bayer
--
Thank you,

James Bayer

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.