Add friendships/lookup about node-twitter HOT 5 CLOSED

@lukaswhite I've just been doing a couple of tests, and it turns out that you can pass screen_name and user_id in the same API call. Do you mind if I go ahead and build this out with the ability for using both params in one request?

from node-twitter.

By all means; the "fix" above isn't doing anything right now, not got as far as a pull request or anything - just waiting on some sort of response.

Out of interest, why would you pass both the screen name and user_id, if they refer to the same user?

from node-twitter.

Flexibility, I guess. I was thinking of a particularly bizarre use case where a user provided something like ['102718482', 'twitterapi']. We can split that into screen_name=twitterapi&user_id=102718482 based on data type, and the response you get returns the user details for both the usernames provided in screen_name, and the id's provided in user_id. The response back from Twitter's API with the above data looks like this (when testing via cURL, anyway):

[ { "name":"Jamie Hoyle", "screen_name":"mightyshakerjnr", "id":102718482, "id_str":"102718482", "connections":[ "none" ] }, { "name":"Twitter API", "screen_name":"twitterapi", "id":6253282, "id_str":"6253282", "connections":[ "none" ] } ]

from node-twitter.

@hyl @lukaswhite I just pushed a new version which introduces a new callback pattern and better support for endpoints that have not been added. If you pull down twitter@1 you can use:

var params  = {};
client.get('friendships/lookup', params, function(error, data){
});

Eventually we will deprecate this helper functions as they will become impossible to scale.

from node-twitter.

@lukaswhite @hyl I will leave this open to keep the id vs screen_name discussion going

from node-twitter.