William

I am also of the opinion that inherited arguments and options should provide validation. The options validation was requested in #901. From my experimentation, the help system code properly supports...

In my case, I'm looking to share arguments rather than options. An example of a possible CLI is a tool that uses an HTTP endpoint to perform some form of...

```C# var inputArg = new Argument("input"); var cmd = new RootCommand { new Argument("serviceUrl"), new Command("base64") { inputArg }.WithHandler(MyHandler), new Command("ascii85") { inputArg }.WithHandler(MyOtherHandler) }; ``` In your example, the...

Using this example, the `serviceUrl` argument appears twice in the help. Once before both the `base64` and `ascii85` verbs and again after each of the verbs. I originally tried something...

The Name from the NRPT table isn't actually used as part of the DNS Suffix Search List. It's used a namespace to limit DNS queries to a specific network interface...

The namespaces from NRPT tables aren't used as DNS Search Suffixes. The DNS Search Suffixes are appended to queries as you already know, the namespace is only used to target...

I appreciate that you took the time to consider this further, but ultimately there appears to still be a disconnect between the usage of the NRPT table and the purpose...

My apologies, I'd convinced myself that the library was adding the DnsSuffix to queries automatically. After reviewing the code again, I see that is only happening in your minidig example.

I believe you meant @william00179

The solution I came up with is: ``` CSharp public static async ValueTask WhereFilter(FluidValue input, FilterArguments filterArguments, TemplateContext templateContext) { // this filter corrects an issue with the builtin where...