When binding to interface collections, config generator shouldn't generate logic for both interface & mapping collection type. #89043
Labels
area-Extensions-Configuration
enhancement
Product code improvement that does NOT require public API changes/additions
size-reduction
Issues impacting final app size primary for size sensitive workloads
source-generator
Indicates an issue with a source generator feature
Milestone
Matching concrete type = actual type to instantiate when binding if needed, e.g.
IList -> List
IDictionary<,> -> Dictionary<,>
Using the
Geolocation
type from @martincostello's repro for #89010, if an interface such asIList<T>
orIDictionary<,>
is the target binding type, the generator emits logic for both the interfaces and matching config types e.g.Generated (buggy output per #89010):
We only need one of these methods.
The text was updated successfully, but these errors were encountered: