db0@lemmy.dbzer0.com to Programmer Humor@programming.dev · 11 months agoThat shadowy placelemmy.dbzer0.comimagemessage-square26fedilinkarrow-up1898arrow-down10
arrow-up1898arrow-down1imageThat shadowy placelemmy.dbzer0.comdb0@lemmy.dbzer0.com to Programmer Humor@programming.dev · 11 months agomessage-square26fedilink
minus-squarebleistift2@sopuli.xyzlinkfedilinkEnglisharrow-up15·11 months agolocation /old_api { redirect /new_api } (can’t be bothered to check the syntax).
minus-squareCosmicTurtle0 [he/him]@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up15·11 months agoIf you have a major version change, it means that old API calls will break against the new API, assuming they are accurately following semver.
minus-squarebleistift2@sopuli.xyzlinkfedilinkEnglisharrow-up13·11 months agoYou’re absolutely right. In my mind “feature parity” got garbled into “backwards compatibility”.
(can’t be bothered to check the syntax).
If you have a major version change, it means that old API calls will break against the new API, assuming they are accurately following semver.
You’re absolutely right. In my mind “feature parity” got garbled into “backwards compatibility”.