Expected behavior for running commands with no elements specified?
Background
At present, all commands that require a list of elements as argument, happily run without any arguments, and even report SUCCESS at the end. This gives the user the impression that something meaningful has happened, when in effect BuildStream hasn't really done much other than parsing the project/user configuration.
I am not sure if this is intentional? If not, we have a couple of options:
- We can raise an error (or at least a warning) that no elements were specified.
- We can "build/show/track/..." everything, similar to
--world
, proposed in !926 (closed) and #640 (closed).
I would personally prefer the first option in order to avoid any surprises.
Task description
-
Agree on how bst
commands should behave when no elements are specified -
Implement the changes for all affected commands.