Handle API Versioning

Question

Handle API Versioning

pwr22 opened this issue 8 years ago · 7 comments

pwr22 commented 8 years ago

Provide a way to specifying the API version wanted

Answer 1 · 2017-03-07T15:34:50.000Z

Why would you want to ever use an old API?

Answer 2 · 2017-03-07T15:39:28.000Z

@mitchcapper I never would but I don't want to preclude the ability to use the next version

Answer 3 · 2017-03-07T17:00:54.000Z

Ah. I would suggest calling this "force_api_version" arg or something similar then, as there is a decent chance just changing to a future version number (of they deprecate the current one) would not just work. Just a name to make it a bit more obvious that things may not work as expected it changed.

Answer 4 · 2017-03-08T11:19:04.000Z

My plan is to have a class per version

Answer 5 · 2017-03-08T23:01:29.000Z

@pwr22
Sounds good, although again if you write the class for V5 for example who would ever want to use V4? That is unless you change the perl interface itself so we are talking about your API migrations and they don't want to update their code before V4 is depreciated.

Answer 6 · 2017-03-09T15:14:06.000Z

Since CloudFlare will only bump the version number again if they make backwards incompatible changes, I expect it would be necessary to make matching changes to the module interface

Answer 7 · 2018-05-14T20:16:33.000Z

Per #2 it seems the deadline for this is June 2nd 2018 now.