Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Originally, I was going to try and build a more structured framework that allowed users to pass, for example, a list of keywords or hashtags or cashtags (etc.), and then have the method build the query. However, building something that can capture the entire functionality of the endpoint package seems like serious overkill. Furthermore, I toyed with the idea of providing some sort of simple functionality (like being able to accept a list of keywords), however, I think this makes things more confusing.
Instead, I provided a lot of details in the docstring which should be sufficient for anyone with half an idea.
This way the user can build the query themselves and pass it directly to the method.