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
I think these two endpoints should only take user IDs, and not implicitly perform the lookup if a username is passed.
This would let us:
avoid the complexity of dealing with usernames that might also user ids (I think the current implementation has some weird edge cases - a username that doesn't exist will raise an error, but a user id that doesn't exist won't)
align the functionality with the Twitter API at the client, rather than doing an unexpected username -> user_id lookup
We'd probably need some supporting documentation to show how to convert usernames into user ids too?
The text was updated successfully, but these errors were encountered:
I think these two endpoints should only take user IDs, and not implicitly perform the lookup if a username is passed.
This would let us:
We'd probably need some supporting documentation to show how to convert usernames into user ids too?
The text was updated successfully, but these errors were encountered: