commandlineparser / commandlineparser/commandline

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

Abierto
#106 1 comentario 0 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
C#
Estrellas
4.8k
Forks
478
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

**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?

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
csharp
Área
cli
Tipo de issue
Nueva funcionalidad
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.