Binder throw ambiguous match exception for object with read only indexer property that has two implementations in base class about bogus HOT 2 OPEN

I've run into this bug just this week and am curious if there's intent on a fix in an upcoming release? I can work around by adding a protected set; to the property, but would love to not have to do this as it reduces the integrity of the instantiated class.

from bogus.

@addixon-cnhi I haven't dived into this particular issue yet, but I suspect one workaround might be to create your own Binder:

• https://github.com/bchavez/Bogus/blob/0f4efc216b9a024d8a6c10c3d106980ff61ce927/Source/Bogus/Binder.cs

The Binder is responsible for reflecting over / introspection of T in Faker<T> to determine what properties/fields are available on T. Also, the original post has a branch with some of the changes that seem to have worked around the original issue.

You can supply your custom Binder here in new Faker<T>(binder: MyCustomBinder):

• Bogus/Source/Bogus/Faker[T].cs

  Line 147 in 0f4efc2

  public Faker(string locale = "en", IBinder binder = null)

Let me know if that helps.

from bogus.