in AuthenticationService.cs the constructor only accepts a "IClaimsTransformationtransform". Is there a reason behind only passing a single IClaimsTransformation in instead of a "IEnumerable<IClaimsTransformation> transform".
Performing a transformation on a piece of data, to me, is something that would make sense to allow multiple things to affect. I was wondering if there is something I overlooked about the implementation or if there is some way built in to the framework to combine transformations on the fly.
My use case is I have a library that I need to set a Claims Transformation on, my concern is what happens if other libraries users are planning to use also need to override the transformation. What is the correct way to perform the override?