Jens Wille

It wasn't clear to me that this issue referred to being able to run Catmandu tests. That's why it's usually beneficial to state one's intention instead of assuming what the...

> Granted, one more class is introduced , but then I like very much small classes. But then you'd have to introduce new classes (and Flux commands) for every other...

> Many parameters make things so complicated (in my view). That's hard to argue with. With great flexibility comes great responsibility ;) But then again, we'd have a unified interface...

Not to rain on your parade, but this is the direction I had in mind: 3f7e150. Maybe this helps to further the discussion.

> Shall we close this branch and further discuss at #463? If you think that's the way to go, then yes. But it wasn't my intention to kill the discussion...

Superseded by #463.

I don't think I have much to add at this point. Except maybe that type 3 could also be useful for [Elasticsearch pagination](https://www.elastic.co/guide/en/elasticsearch/reference/8.4/paginate-search-results.html) (`search_after` and/or `scroll`).

> In general, I think we should implement this like the existing lookup, so something like: > > `lookup("subject.label", "rpb.ttl", someOption: ..., anotherOption2: ...)` Are you sure that `lookup()` should...

> My view would be that essentially, we want to support one additional file format, TTL, in addition to CSV and TSV. In principle, yes, but [`lookup()`](https://metacpan.org/pod/Catmandu::Fix::lookup) is specifically meant...

Could you elaborate a little? > Group commands by type What is a command's type? > Explain signatures What might such an explanation look like? > Add missing options Which...