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 also noticed that the replies are housed in threaded_conversation_with_injections_v2
The field shows up in the output if I set with_tweet_replies to False
On the other hand, the same field is not showing up in the output if I set with_tweet_replies to True
The field where the replies are is in the itemContent field
While this does not break the main use of disabling with_tweet_replies which is to use the endpoint without a session, it still makes the output huge.
A temporary solution whould be checking "entries":[], finding every "content": {} block that has "__typename": "TimelineTimelineModule", and cleaning them out of the output.
I would like to know if anyone else is experiencing the same issue.
Let's have a discussion in this thread. Cheers everyone!
The text was updated successfully, but these errors were encountered:
Hi @iSarabjitDhiman! First of all, great job in building this package.
Upon using the package, I noticed that
with_tweet_replies
is still returning replies even if its value is set to FalseI am using
with_tweet_replies
forget_tweet()
:I also noticed that the replies are housed in
threaded_conversation_with_injections_v2
The field shows up in the output if I set
with_tweet_replies
toFalse
On the other hand, the same field is not showing up in the output if I set
with_tweet_replies
toTrue
The field where the replies are is in the
itemContent
fieldWhile this does not break the main use of disabling
with_tweet_replies
which is to use the endpoint without a session, it still makes the output huge.A temporary solution whould be checking
"entries":[]
, finding every"content": {}
block that has"__typename": "TimelineTimelineModule",
and cleaning them out of the output.I would like to know if anyone else is experiencing the same issue.
Let's have a discussion in this thread. Cheers everyone!
The text was updated successfully, but these errors were encountered: