@[email protected]M to [email protected]English • 5 days agoBreaking Changes in Lemmy 1.0join-lemmy.orgmessage-square46fedilinkarrow-up1177arrow-down10cross-posted to: voyagerappthunder_appsyncforlemmy[email protected]thunder_appsummitarcticboostforlemmy[email protected]
arrow-up1177arrow-down1external-linkBreaking Changes in Lemmy 1.0join-lemmy.org@[email protected]M to [email protected]English • 5 days agomessage-square46fedilinkcross-posted to: voyagerappthunder_appsyncforlemmy[email protected]thunder_appsummitarcticboostforlemmy[email protected]
minus-squaredavel [he/him]linkfedilinkEnglish18•5 days agoA lot of these should not be called breaking changes. A new API is not a breaking change if the old API remains.
minus-squarenfhlinkEnglish4•5 days agoYeah but those changes break clients as soon as they turn down the old API.
minus-squaredavel [he/him]linkfedilinkEnglish13•5 days agoIndeed, dropping the old API would be the breaking change. Rich Hickey did a fantastic talk on versioning, breaking changes, and dependencies.
A lot of these should not be called breaking changes. A new API is not a breaking change if the old API remains.
Yeah but those changes break clients as soon as they turn down the old API.
Indeed, dropping the old API would be the breaking change.
Rich Hickey did a fantastic talk on versioning, breaking changes, and dependencies.