Feature Request: Output into stdout

[vladkorotnev]

Thanks for the very useful tool!

I would like to suggest that outputting into stdout might be a very useful addition to using this tool in various pipelines :-)

Currently I was able to capture the output by using mkfifo and juggling around with it, but if something goes wrong (e.g. Package.resolved is not in a current state so the tool crashes with a "file not found" error), the other end of the pipeline reading from the fifo gets stuck and has to time out...

[FelixHerrmann]

Hey @vladkorotnev, thanks for the request. This is definitely a valuable addition to the tool, I will take a closer look to this when I find some time.

Just to clarify, there should be a flag which controls if the output as JSON or property list (PDF and settings bundle doesn't make sense) gets printed to the console instead of writing it to a file, right?

[vladkorotnev]

Hello, Yes, that is the assumption. A more expected way (inline with other tools bundled with the OS and the like) would be defaulting to that, unless specified otherwise with the flags. I tried to look around the code but only a very little bit, so it didn't seem to be easy for someone outside of the project like myself sadly Best regards,

…

On Wed, May 10, 2023, 23:49 Felix Herrmann ***@***.***> wrote: Hey @vladkorotnev <https://github.com/vladkorotnev>, thanks for the request. This is definitely a valuable addition to the tool, I will take a closer look to this when I find some time. Just to clarify, there should be a flag which controls if the output as JSON or property list (PDF and settings bundle doesn't make sense) gets printed to the console instead of writing it to a file, right? — Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFAGQSUIC64OOGHVDZRPUTXFOTGVANCNFSM6AAAAAAX4G3A4M> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[FelixHerrmann]

Hi @vladkorotnev, I've just added this functionality but it requires a major version release. It is accessible via a scan subcommand so you just have to add it to your existing configuration, e.g. swift-package-list scan ~/Desktop/Test/Test.xcodeproj.

[FelixHerrmann]

Version is live, let me know if something needs to be adjusted!