I'm uncertain whether this is a real bug or a wrong unit tests.
Basically: registrations in the CacheOutputConfiguration will only take into account whateve is used in the first invocation due to the inner implmentation with GetOrAdd.
That's fine if is the intended behaviour, but then the CacheKeyGeneratorRegistrationTests.last_registered_default_is_used states other thing.
Due to a strange combination this was not breaking test itself, you can check comment about that.
I'm uncertain whether this is a real bug or a wrong unit tests.
Basically: registrations in the
CacheOutputConfigurationwill only take into account whateve is used in the first invocation due to the inner implmentation withGetOrAdd.That's fine if is the intended behaviour, but then the
CacheKeyGeneratorRegistrationTests.last_registered_default_is_usedstates other thing.Due to a strange combination this was not breaking test itself, you can check comment about that.