You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Haven't seen this in the other Twitter libraries. Presumably it would help with issues like ttezel/twit#415, though it's probably better to abstract the resource subdomains from the user.
The text was updated successfully, but these errors were encountered:
@dandv It's been a while for this issue, but I think you make an important point. What is the best way to handle Twitter endpoints that don't start with api.twitter.com (for example, publish.twitter.com). Right now we just pass in a string to the constructor like this:
constclient=newTwitter({subdomain: "api",// this could be "publish", for exampleconsumer_key: "abc",// from Twitter.consumer_secret: "def",// from Twitter.access_token_key: "uvw",// from your User (oauth_token)access_token_secret: "xyz"// from your User (oauth_token_secret)});
When you say "it's probably better to abstract the resource subdomains from the user", what do you have in mind? Would we want a full-fledged object that corresponds to each subdomain like this?
// instead ofclient.get("statuses/show",{...})// we haveclient.statuses.show({...})
Haven't seen this in the other Twitter libraries. Presumably it would help with issues like ttezel/twit#415, though it's probably better to abstract the resource subdomains from the user.
The text was updated successfully, but these errors were encountered: