Open DavSanchez opened 3 years ago
I may be interested in implementing support for at least some of the v2 api (as I want it myself), but I'm not sure how I would structure that within this same package. Would you want some kind of namespacing, @himura ? Should we put everything v1 in one place (possibly breaking backwards compatibility) and v2 in another, or should we just add v2 in a new place while keeping the v1 stuff as-is, or something else?
Hi,
First of all congratulations for your work, it's a pleasure to work with
twitter-conduit
! I was wondering if support for the new Twitter API v2 is planned for this library. I could take advantage of some of its functionalities... Thanks and regards!