Design: `onyo tree`

[aqw]

onyo tree should be rewritten.

The current functionality lists everything or optionally allows filtering for directories (which includes asset directories).

The purpose of this "directories" view is to see the scaffolding of a repo without the assets. This is easy enough to address: change "directories only" into "no assets" (files or directories).

However, given the prevalence of ideas to use asset directories more and more (and to the point where the idea has been floated to remove the concept of non-asset directories), "scaffolding" is really in the eye of the beholder. And a "no assets" filtering is too naive.

What is probably necessary is for tree to gain get's filtering skills. This is already possible out-of-the-box:

onyo get --machine-readable --types assets directories --keys onyo.path.relative --match type!=laptop | tree --fromfile

The upshot of this approach is that it encourages our idiom of piping get's output into other utilities. However, it's not exactly ergonomic, and I certainly wasn't aware (until recently) of tree --fromfile.

So I wonder if onyo tree should continue to live on, and act basically as an alias for

onyo get --machine-readable --types assets directories --keys onyo.path.relative | tree --fromfile

That would be the default, and users could override those options as necessary (with the normal use-case of adding --match statements).