commandlineparser / commandlineparser/commandline
Most effective way of working with IoC containers and injected verbs?
- Linguagem predominante
- C#
- Estrelas
- 4.8k
- Forks
- 478
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
**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?
Guia de contribuição
Nenhum guia de contribuição indexado para este repositório
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- csharp
- Domínio
- cli
- Tipo de issue
- Funcionalidade
- Dificuldade
- 5/5
- Tempo estimado
- Mais de uma semana
- Status de atividade
- Estagnada
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 25/100