Open TCLamnidis opened 9 months ago
Sound like a good idea to me :+1:
What would be a solid interface for this? Just a --verbose
(?) flag that adds all of these columns to the output? Or a more sophisticated argument to request specific columns?
IMO spitting out all the info in the YAML file with one flag is enough. It's easy enough to select a subset of columns downstream if need be.
The main thing for my use case here is the package_directory
column, which is not in the YANL, but implicitly known (as the path to the file)
This is contingent on an update to the server API, since list
also needs to feature --remote
, so any listing we perform here must be possible also from the server. So this issue is somewhat contingent on #272 and #273. And I'm working on those.
After talking with Stephan today, we thought it would be nice to have the option of getting more information about ecah package out of trident list. This would streamline integration into data analysis, and also downstream processes (like thetis).
Below is an example of a TSV with information contained in the POSEIDON.yml of 2 packages as a reference:
trident list --remote --packages --raw
already shows some of this information, so adding more columns to the ouput with a dedicated flag would do the trick.