• CosmicTurtle0@lemmy.dbzer0.comEnglish
      18·
      18 dni temu

      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.

      • bleistift2@sopuli.xyzEnglish
        15·
        18 dni temu

        You’re absolutely right. In my mind “feature parity” got garbled into “backwards compatibility”.

      • Longpork3@lemmy.nz
        21·
        18 dni temu

        A translation layer could be used, no? Check api version, translate any v1 specific calls into their v2 counterparts, then submit the v2 request?

        • CosmicTurtle0@lemmy.dbzer0.comEnglish
          2·
          18 dni temu

          This isn’t really efficient because when v2 gets updated now you have to update the translation layer as well.

          Any improvements you made in v2 would likely not translate.

          Essentially the best way is to provide users with an incentive to switch. Perhaps a new feature or more requests.