Is there a reason that filter and list are different goals I

Question

Is there a reason that filter and list are different goals It seems like filter is a superset of list functionality

loud-laptop-17949 · Answer

I ask because I want to make use of the new cli aliases feature but all my useful ones require piping filter and list calls together

hundreds-father-404 · Answer

You re right that filter is a superset of list There is technically the `list documented` feature but that s weird and can now be replaced probably by using the `peek` goal with JQ I think we could merge filter into list Benefit is one fewer goals I suppose

loud-laptop-17949 · Answer

yeah

loud-laptop-17949 · Answer

or maybe add the filter params to all relevant goals

loud-laptop-17949 · Answer

` pants filter target type=shell sources fmt` rather than ` pants filter filter target type=shell sources | xargs pants fmt`

hundreds-father-404 · Answer

Yeah that s probably a better approach

curved-television-6568 · Answer

I was pondering what it would look like to support piping aliases into own runs something like ``` cli alias cmd = | filter ``` target type= But wasn t sure how to use that in a useful way Having the filter args support for all targets makes a lot more sense

loud-laptop-17949 · Answer

yeah i would suggest trying to avoid piping there git aliases support it though