-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add profile_banner_url to v2 User object #13
Comments
Hi @HitomaruKonpaku - thank you for your suggestion. The process for the Open Evolution repository shows how you can go about having this feature considered by our engineering team. We require a Pull Request to be submitted following the appropriate template before we will initiate a formal internal review process. This issue is a great start, as a discussion. Can you expand on why this is a useful addition for you / what the wider use case is, and how you might expect to have the data returned from the API? |
Hi @andypiper , thank you for your reply. As I see in the process, I should make an issue to discuss about it before actually making a PR, so I landed here. As for the I expect to have nullable
|
Can't this field be added yet? Everyone needs him so much. Waiting too long? |
Just a reminder that in order to contribute a feature for direct consideration by the engineering team, there's a workflow via opening a pull request on this repository, that requires a specific format. As an additional reminder, if you'd like to participate in the discussion please be respectful and follow the Twitter OSS code of conduct. Thank you! |
created #31 |
@metaglobal @HitomaruKonpaku @andypiper see submitted pull request |
Unfortunately I’m no longer able to work on this project. |
@andypiper too bad for us. |
Any new on this? In 5 days the v1 API will stop working and there is not an alternative in v2? |
Hi,
As title said, can we have
profile_banner_url
return in API v2 users lookup?I saw many people asking for it too. See: https://twittercommunity.com/t/profile-banner-url/155807
The text was updated successfully, but these errors were encountered: