Add a new category in debug visualizer for Castle Windsor
The debug visualizer lists components that may be misconfigured, because the container does not know how to resolve all their dependencies. However, components show up here even if there is also registered a factory that will supply these dependencies. So, I don't really see these as "potentially misconfigured", though certainly some code could ask the container to resolve directly rather than going through the factory.
I'd still like to know about these components, but they seem a bit "noisy" when lumped with components that really cannot be resolved.
I think it would be helpful to add a separate category to the visualizer, something like "Components that can only be resolved through a factory".
The more I think about this, the less I'm confident there's a good way to solve it, other than having a whitelist of well known (internal) components that we know are meant to be only used with factories (like the TypedFactoryInterceptor)
Every misconfigured component may be resolved via a factory
Thanks, Krzysztof. I'm OK with whatever you decide. Just trying to reduce the noise a bit so that the list of "potentially misconfigured" components is a bit more meaningful.
I am loving Castle Windsor. Keep up the good work!
I do agree it is kind of noisy. I'm not sure though If creating a new category is the best approach. Perhaps just marking these in some special way would suffice...