db0@lemmy.dbzer0.com to Programmer Humor@programming.dev · 5 days agoThat shadowy placelemmy.dbzer0.comimagemessage-square29fedilinkarrow-up122arrow-down10
arrow-up122arrow-down1imageThat shadowy placelemmy.dbzer0.comdb0@lemmy.dbzer0.com to Programmer Humor@programming.dev · 5 days agomessage-square29fedilink
minus-squarebleistift2@sopuli.xyzlinkfedilinkEnglisharrow-up1·5 days agolocation /old_api { redirect /new_api } (can’t be bothered to check the syntax).
minus-squareCosmicTurtle0@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up1·5 days 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-up1·5 days 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”.