The ContainerUncontrolledServicesDecoratorInterceptor contains the following remark:
// Because the user registered an IEnumerable, this collection can be dynamic in nature,
// and the number of elements could change on each enumeration. It's impossible to detect if a
// returned element is supposed to be a new element and should get its own new decorator, or if
// it is supposed to be an existing element, for which an already cached decorator can be used.
// In fact we can't really cache elements as Singleton, but since this was already supported in
// the past, we don't want to introduce (yet another) breaking change.
This backwards compatibility feature has been in place for many years. It's time to ditch support for singleton decorators on container-uncontrolled collections.
The text was updated successfully, but these errors were encountered: