Skip to content
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

Way to pass expanded paramaters in filteredstream? #22

Open
saadmanrafat opened this issue Jan 18, 2022 Discussed in #20 · 0 comments
Open

Way to pass expanded paramaters in filteredstream? #22

saadmanrafat opened this issue Jan 18, 2022 Discussed in #20 · 0 comments

Comments

@saadmanrafat
Copy link
Member

Discussed in #20

Originally posted by SolidHabu January 18, 2022
So I noticed in all other examples, simply subclassing the *Stream class and adding the appropriate query params as variables would make the stream work. However, in FilteredStream this seems like it won't work properly, as I still get the default tweet object output back when connecting to the stream.

Does this actually work and I am being dense? or is it something not yet implemented for filteredstream yet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant