What is the preferred flow of returning results from CommandHandler

[mmierzwa11]

Should I just call Console.WriteLine in CommandHandler or is it somehow possible to return object and somewhere at lower level catch all result and do generic Render operation. Also I have cloned repo, and tried to get RenderingPlayground project to work, but it doesn't work as expected, I tried running this sample in cmd and powershell and both can't render many samples correcty. But if I change consoleRenderer OutputMode explicitly to Ansi it seems to start working, could you please provide basic scenario of real world usage of System.CommandLine.Rendering and maybe result handling from CommandHandler?

[jonsequitur]

System.CommandLine.Rendering isn't set up currently to demonstrate automatic detection of the terminal capabilities. You can use rendering directives to try out the different modes. See #509 for more details.

Should I just call Console.WriteLine in CommandHandler or is it somehow possible to return object and somewhere at lower level catch all result and do generic Render operation.

Something like this is being considered for this API, rather than just returning result codes. Currently though all output needs to be written directly to System.Console or through an IConsole instance passed to your handler.

[seanalford]

I'm passing a delegate to the command handler to get the results back.

public static Command Create(HttpClient client, string apiPath, string name, string description, Action<HttpResponseMessage,List< T>> responseAction)
{
Command command = new Command(name, description);
command.Handler = CommandHandler.Create(async () =>
{
HttpResponseMessage response = await client.GetAsync($"{apiPath}");
List data = await response.Content.ReadAsAsync<List>();
responseAction(response,data);
});
return command;
}