Open tonivdv opened 6 years ago
This is actually something we've been looking into. Do you ever use multiple versions, or would pinning library versions to a single API version also work?
In our case, we are not using multiple versions. So if you would release a single API version library that would fit our needs! ;)
Hey @christopherseeley ,
Is this still on the roadmap?
Cheers
It's still on our radar but being actively worked on at this time.
@christopherseeley let's hope it comes out soon. We just had to do an update to be aligned with latest version and it means a PR of +200 files 😅
On a related note, is it possible to expose an API or query of some sort via these libraries to "ask" the API if it is still valid or deprecated (before it is completely sunset)? This way, we could set up monitor in our system to auto-create a task for us when/before the version we are using becomes deprecated (thus preventing potential last-minute fire drills or production outages).
We have a CSV with the deprecation and sunset dates available: https://developers.google.com/ad-manager/downloads/api-schedule.csv
You could have a CI system pull this in and scan your code for imports of a version that is deprecated or will be soon.
@christopherseeley - whoa! That should work great! Thanks!!
Hey DFP team,
Would it be possible to imagine to have a "package" called "latest" which points to the current latest version of the API ?
Example, currently we have
com.google.api.ads.dfp.axis.v201805
as latest version. So the content of this would also be made available via packagecom.google.api.ads.dfp.axis.vlatest
.Integrators who always want to be using latest version only need to update their dependencies. But that's the only thing they would have to do. Currently we must manually update all our source code to change the version in the package name. Needless to say this is a real pain in the neck!
PS: this is not only related to this library, but all other wrappers in the different languages (php , etc)
Hope it's possible.
Thanks