search

salesforce-marketingcloud / SFDC-MC-REST-Style-Guide

REST style guidelines
31 stars 9 forks source link

Subversioning #2

Open sprshrp opened 9 years ago

sprshrp commented 9 years ago

We'd do well to respect customers who cannot handle (despite being warned that they should) even non breaking changes to objects.

aroden-salesforce commented 9 years ago

A breaking change requires a new version. This addition means changing anything on our end bump the version. How can customer's ask for the old version?

Further, developers are unlikely to keep "Content-Version" header accurate. Having no information feels better to me than wrong information.

ncorn commented 9 years ago

What we have thus far is pretty explicit about not allowing this. Only breaking changes in a version bump which is scoped as the entire platform (by the version being the first URL segment).

sprshrp commented 9 years ago

@ncorn This should be read as specific to identifying non-breaking changes to resources, will modify.
@aroden-salesforce Not sure if we MUST (although we SHOULD) support querying the old version, just want to give them an indication that a change was made.