BstBln

4 ms·

1. 1.▲
   by BstBln 7y ago

   I think so too, but even in case one disagrees, they should have mentioned it. Otherwise you’d think they never had heard of it :)
2. 2.▲
   by BstBln 7y ago

   Also seems they never heard about versioning via content negotiation :)
3. 3.▲
   by BstBln 7y ago

   "Services MUST increment their version number in response to any breaking API change. See the following section for a detailed discussion of what constitutes a breaking change. Services MAY increment their version number for nonbreakin
4. 4.▲
   by BstBln 7y ago

   Indeed :)
5. 5.▲
   by BstBln 7y ago

   Especially they are suggesting that if not mentioned in the docs, a non-breaking add of a field should result in a new api version...
6. 6.▲
   by BstBln 7y ago

   Assuming you’re working with JSON, it’s very easy to ignore extra fields and no reason to deploy any fixes for that :)
7. 7.▲
   by BstBln 7y ago

   „Some services MAY add fields to responses without changing versions numbers. Services that do so MUST make this clear in their documentation“ WTF
8. 8.▲
   First German in Space Died(dw.com)

   3 points by BstBln 7y ago|0 comments