Andreas
Andreas
So after some further investigation, I think that the `CommandTreeTokenizer` does a few things that are problematic... Lets say, that you have an array of arguments like this: ```bash cli-tester...
> This is a pretty extreme edge case - relying on shells to act consistently with quotes is simply a non-starter as the link in the previous issue talk about....
@phil-scott-78 @patriksvensson I would really love to get a reply here, I'm trying to help improving this great library... can someone of you at least confirm this problem is part...
> As this in independent of spectreconsole, I struggle to see how consistent handling of various quoted arguments can be addressed within spectre itself, and as @phil-scott-78 pointed out above,...
> Ok, apologies if I totally misunderstood - I see your comments are about what happens once quotes have made their way into the argument (one way or another). I’ll...
> Ok, I can reproduce what you have reported across several bug reports and the discussion thread (https://github.com/spectreconsole/spectre.console/discussions/1025) with the following unit test: Awesome :-) > I don't mind having...
You sir, deserve a cookie! Maybe it would be a good idea to implement the `args` parser framework / library agnostic. ```c# class SubCommand { public string Name; } class...
> Regarding handling of quotes, hyphens and spaces - do you see any cases I've missed? Maybe. I don't see the following (maybe this is intended): - `"\"quoted\" string"` (Quoted...
> I'm starting to suspect that unit testing the POSIX compliant parsing should trim each argument received in the string[] args array Oh, please don't do that! Trying to fix...
> Ok fair enough. I'm just in the middle of mental gymnastics, trying to think of all the unit test cases to support. And what not to support. No offense....