News for hackers. Stuff that matters.

A comment on APIs as infrastructure: future-proofing Stripe with versioning. Parent comment

Re:APIs as infrastructure: future-proofing Stripe with versi... by pbreit on Tuesday August 15, 2017 @09:43PM (#15024343)
If you can do an XSLT transformation to different versions I wonder how important the change was in the first place?
[ Parent | on HN ]
Re:APIs as infrastructure: future-proofing Stripe with versi... by masklinn on Wednesday August 16, 2017 @04:04AM (#15025742)
As TFA notes, replacing a boolean with an enumeration is a breaking change, but can be transformed back easily enough assuming the enumeration just increases the granularity of the original states.

And SOAP is usually schema-verified, so adding fields will generally be a breaking change.

[ Parent | on HN ]
Re:APIs as infrastructure: future-proofing Stripe with versi... by organsnyder on Tuesday August 15, 2017 @10:35PM (#15024549)
Our most common case for this is adding a field to a data model: that will break a SOAP client. The XSLT just strips out the new field.
[ Parent | on HN ]