Skip to content

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

@igorbrigadir

Description

@igorbrigadir

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    cliIssues with command line interfacedocumentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions