commandlineparser / commandlineparser/commandline

Most effective way of working with IoC containers and injected verbs?

未關閉
#106 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
C#
星號
4.8k
分支
478
PR 合併指標
30 天內沒有已合併 PR

描述

**Issue by [dmoonfire](https://github.com/dmoonfire)**
_Sunday Jan 15, 2017 at 05:14 GMT_
_Originally opened as https://github.com/gsscoder/commandline/issues/404_

----

So, I'm fond of IoC builders (Autofac, Ninject, etc). We are building up a command line that has pluggable verbs. In most cases, the IoC containers return actual instances of objects, not types. I'm currently using the system to build up a list of types.

```csharp
var container = ...;
var verb = container.Resolve();
var verbTypes = verb.Select(v => v.GetType()).ToArray();
var results = Parser.Default.ParseArguments(args, verbTypes);
```

This can be inefficient. Is there a way of putting the resolved classes directly in without using types or knowing all the verbs ahead of time?

貢獻指南

這個儲存庫沒有索引到貢獻指南

研究方向

Start by reading the Parser.Default.ParseArguments call and the ICommands resolution example in the issue. Determine whether the parser supports resolved command instances instead of verb types without knowing verbs ahead of time. Done would be a documented supported approach or a clearly recorded limitation.

由索引模型根據 Issue 內容生成。

評估

技術堆疊
csharp
領域
cli
Issue 類型
功能
難度
5/5
預估耗時
一週以上
活躍度
停滯
描述清晰度
需要釐清
新手友好度
25/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。