entities.hashtags
patrick-lee-warren opened this issue · 3 comments
patrick-lee-warren commented
In V1 API, there was a field called entities.hashtags. I include "entities" in my config file, but it doesn't come through. Is it available?
dhudsmith commented
The entities object is a big nested structure with arrays making it not easy to flatten for the csv. That being said, it wouldn't be too hard to just dump that nested structure in a new column for each tweet record. Would this be good enough?
patrick-lee-warren commented
That would be good enough for me. Hashtags are just about convenience,
because I can pull them from the tweet. But some of the other entities are
otherwise inaccessible.
PLW
…On Wed, Oct 27, 2021, 11:59 AM Hudson ***@***.***> wrote:
The entities object is a big nested structure with arrays making it not
easy to flatten for the csv. That being said, it wouldn't be too hard to
just dump that nested structure in a new column for each tweet record.
Would this be good enough?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKBA7BQNPSWYGFE666KZ6C3UJAOXJANCNFSM5GY7RCYA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
dhudsmith commented
Adding 'entities' to 'tweet_fields' in the config now works correctly. Entities are saved in the data_tweets.csv file under the 'entities' column.