Update client frequency
Closed this issue · 4 comments
There was bunch of activity in https://github.com/Asana/asana-api-meta with many resources missing from python client. Can this client library be updated to have these fresh resources?
Can we have this client be updated regularly, possibly in CI manner, as soon as there is change in https://github.com/Asana/asana-api-meta repository, please. Ideally it should autopublish to pypi as well ;)
CC: @rossgrambo
It look like there should be tag/travis-api-meta-incoming-push/pull-request dance happening. Thus question turns into: When do we expect fresh tag? Last one is more then a year old.
Hey @myroslav I see you and @rossgrambo have been chatting about this in our forums at https://forum.asana.com/t/topicality-of-official-asana-sdks/50951. We did discuss doing this very soon (this sprint) but it does end up being a non-trivial amount of work to get done because the update cycles involve updating all of asana-api-meta, python-asana, ruby-asana, php-asana, java-asana... and each of our client libraries has ideosyncratic behavior to them. The goal of that is to make python-asana, for instance, "feel pythonic" but it is architected completely differently than even ruby-asana, which one would think would be pretty similar.
That being said, the reason it's been so long is because we're working on rolling out a better solution that will make these updates more frequent, but we know we're behind on updating our current libraries. Keep a lookout for updates to come very soon whenever we can shift our focus back to them (probably a few weeks but not do far out as a few months)!
I see "manual" PR at #88.
Will this procedure be standard, or tagging of https://github.com/Asana/asana-api-meta is expected to initiate other SDKs update as well?
Once we finish our better solution, all the SDKs will auto update when we do the tagging.
Until then, we need to manually do the PRs, as the generated code isn't enough on it's own.