Is there a way to get and log the constructed cli arguments before invocation?

[ptr727]

I am trying to consolidate my arg creation to use the .WithArguments(args =>args.Add(fileName).Add("foo") pattern.
But with this pattern I cannot log the args before process invocation, or at least I don't know how to get access the constructed argument list from the builder.

If I use this pattern it is sequential but I can log all arguments I pass.

  string[] arguments = [ fileName, "foo" ];
  Log.Debug("Calling ffmpeg with {Arguments}", arguments);
  BufferedCommandResult result = await Cli.Wrap("ffmpeg")
      .WithArguments(arguments)
      .ExecuteBufferedAsync(cancellationToken);

Is there a way to enable logging or args before process launch, or a way to e.g. .AndLogArgs(args => Log.Debug("Calling ffmpeg with {Arguments}", args), or have the builder call a lambda that can pre-process / view the generated arguments?

[Tyrrrz]

You have two options:

1. Separate the command initialization from execution and use the Command.Arguments property:

var cmd = Cli.Wrap("ffmpeg").WithArguments(...);
var arguments = cmd.Arguments; // string
var result = await cmd.ExecuteBufferedAsync(...);

2. Build the arguments outside of WithAguments(...):

var arguments = new ArgumentsBuilder().Add(fileName).Add("foo").Build(); // string
var result = await Cli.Wrap("ffmpeg")
    .WithArguments(arguments)
    .ExecuteBufferedAsync(cancellationToken);

[ptr727]

Ah, I didn't know I could use Argumentsbuilder standalone, that works, and I can also use it internal from my task builders.