-
-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pass-through arguments #39
Comments
Hiya, I found your tool from a reference and hadn't seen it before. I've been contributing to CommandDotNet. We implemented pass-through. Well, we had pass-through but realized I'd forgotten about the end-of-options feature which was the original reason If you're not aware of it, this may be interesting reading
This allows users to specify argument values that look like options, like |
Yep, I'm aware. Thanks! |
Add support for path-through arguments.
Sometimes the application may act as a proxy to another application. An example of this is
dotnet run
which routes any arguments after--
directly to the executed application.Example:
Arguments
arg1
,arg2
,--flag
are passed as is to the executed application.Allow
[CommandArgumentSink]
attribute on properties of typeIEnumerable<string>
or any other type that can be assigned from a string array or initialized with a string array (similar to how we do conversions currently). There can only be one such property.Note: this has to play nicely with #38.
Open question:
--
only be consumed by argument sinks?The text was updated successfully, but these errors were encountered: