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

Impossible to specify No expansions at all in CLI. #693

Open
igorbrigadir opened this issue Feb 15, 2023 · 0 comments
Open

Impossible to specify No expansions at all in CLI. #693

igorbrigadir opened this issue Feb 15, 2023 · 0 comments
Labels
cli Issues with command line interface documentation

Comments

@igorbrigadir
Copy link
Contributor

I just noticed the CLI won't actually allow you to specify no expansions - sometimes this is desirable, at a minimum, you must specify at least 1 expansion, otherwise the default is applied, which is all expansions.

This won't work to get a minimal representation:

twarc2 tweet 1404396331897085955 --expansions "" --tweet-fields "id,text" | jq

You need to specify at least 1, usually the geo one works well because it's rare:

twarc2 tweet 1404396331897085955 --expansions "geo.place_id" --tweet-fields "id,text" | jq

Also, this tweet example also automatically returns withheld fields, which are not documented as "default" fields that are always returned like id and text, but seem to behave that way.

Personally, I think this is more of a usability edge case thing that may be "fixed" with documentation rather than implementing this in code. But just here for reference.

@igorbrigadir igorbrigadir added documentation cli Issues with command line interface labels Feb 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli Issues with command line interface documentation
Projects
None yet
Development

No branches or pull requests

1 participant