I've updated the Etsy rubygem to use the new oauth/login requirements.
It still uses the old api urls, I'll be migrating these over as soon as I can.
This hasn't been released to rubyforge yet, but if you're using
bundler you can pull directly from github here:
# in Gemfile
gem 'etsy', :git => 'git://github.com/reagent/etsy.git'
Cheers,
Katrina
I maintain a Cocoa client library. I want to get back into the spirit
of things and complete the v2 implementation.
Since the API is becoming quite large, would you care to share your
strategies in keeping up with it?
Wondering if its worth maintaining a community run JSON description of
the API that we can all feed off.
Thanks.
> --
> You received this message because you are subscribed to the Google Groups "Etsy API V2" group.
> To post to this group, send email to etsy-...@googlegroups.com.
> To unsubscribe from this group, send email to etsy-api-v2...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/etsy-api-v2?hl=en.
>
>
Here's my strategy so far... just implement the bits that I've needed,
or that other people have complained were missing :)
In one case, a guy submitted a patch for a piece that I haven't covered.
I'm not sure I have time to help maintain documentation, but if it
exists and I have input, I'd definitely contribute.
Cheers!
Katrina
I came to the same conclusion about getMethodTable and have seen
similar posts here before. Problem is there isn't a method / feed that
outlines resource fields and associations.
I believe its been a feature request in the past and it's not in
Etsy's current plan to implement it.
Thanks.