Chaining identical decorators causes incorrect diagnostic error

[dotnetjunkie]

The details for this bug can be found here: https://stackoverflow.com/questions/69155688/simpleinjector-how-to-reuse-a-decorator-class-more-than-once-in-objects-decora

container.Register<ITarget, Target>(Lifestyle.Scoped);
container.RegisterDecorator(typeof(ITarget), typeof(InstrumentationTargetDecorator), Lifestyle.Scoped);
container.RegisterDecorator(typeof(ITarget), typeof(ResilienceTargetDecorator), Lifestyle.Scoped);
container.RegisterDecorator(typeof(ITarget), typeof(InstrumentationTargetDecorator), Lifestyle.Scoped);

Error:

-[Ambiguous Lifestyles] The registration for ITarget (Async Scoped) maps to the same implementation (InstrumentationTargetDecorator) as the registration for ITarget (Scoped) does, but the registration maps to a different lifestyle. This will cause each registration to resolve to a different instance.

[dotnetjunkie]

Branch bug-925 created.

[dotnetjunkie]

Workaround:

// Make a derivative of the duplicate decorator and register this
class Derivative: InstrumentationTargetDecorator { ...}

container.Register<ITarget, Target>(Lifestyle.Scoped);
container.RegisterDecorator(typeof(ITarget), typeof(InstrumentationTargetDecorator), Lifestyle.Scoped);
container.RegisterDecorator(typeof(ITarget), typeof(ResilienceTargetDecorator), Lifestyle.Scoped);
container.RegisterDecorator(typeof(ITarget), typeof(Derivative), Lifestyle.Scoped);

[dotnetjunkie]

A fix for this issue has been implemented in v5.3.3.