The current default behaviour is that lists within an object are always null if the property is e.g IReadonlyCollection, is there a way that AutoFaker always creates an empty list instead of null?

Is there a way to configure this, without creating a custom binder?

I would also like to create a FakeItEasy fake if the property of an object is an abstract or interface type?

Note:
With the original AutoFaker this was quite easy because the method of the class AutoFakerBinder: "CreateInstance(AutoFakerContext..)" was declared as virtual.

Br

I might be missing that this is already built-in, but it would be super awesome to be able to build configuration via With(e => e.Name), .Without, etc.. I understand it's slower, but subclassing overrides per-class kind of stinks - especially when I could have many different overrides for the same class, I feel like it's harder to grok. Thoughts?

In the docs you mention AutoFakerOverrides which as far as I can tell is not a class in this project.

autoFaker.Config.Overrides = new AutoFakerOverrides();
autoFaker.Config.Overrides.Add(new OrderOverride());

Am I missing something?

Hello, Jake!

You've stated that one of this project goals is to Be fast.

I believe that using code generation is faster than using reflection, and (correct me if I'm wrong) current implementation of Binder is using the reflection. Are there any plans to use the code generation?

If I have an object Person

public class Person
{
    public Person(string firstName, string lastName, int age)
    {
        FirstName = firstName;
        LastName = lastName;
        Age = age;
    }
    
    public string FirstName { get; }
    public string LastName { get; }
    public int Age { get; }
}

That I want to populate with AutoBogus. How can I customise the instantiation?

If I follow the documentation I believe I need the following:

public class PersonOverride : AutoFakerOverride<Person>
{
    public override void Generate(AutoFakerOverrideContext context)
    {
        var target = (context.Instance as Person)!;
        
        target.FirstName = context.Faker.Person.FirstName;
    }
}

However, that will not compile as the FirstName property does not have a public set accessor.

When trying to generate multiple entities it's generating nullable entries. Seems it's not a drop-in replacement for AutoBogus. I am using NUnit as testing engine with parallel execution enabled.

Hi,

Thanks for creating this fork and awesome that soms issues has been solved.

From: nickdodd79/AutoBogus#108

Due to the performance issues and missing types etc I've decided to build an updated version of AutoBogus: soenneker.utils.autobogus

It aims to be a drop in replacement.

Is this really a drop in replacement?

• I would expect that the version number would start with 2.14 (or 2.13.2), as the latest Bogus version is 2.13.1
• There are many new dependencies in this package. Is that really needed? Sure we need the cache. But why the extensions, the smartenums etc. It would make it very hard to port the fixes to AutoBogus back when it's alive again
• Why did we move from .NET Standard to .NET 6?
  • Also, why is the package multi-target package (compiled to .NET 6, 7 and 8)? Are there any code changes between .NET 6/7/8?
• If we need breaking changes, is this possible? As it won't be a drop in replacement

Also, I'm not sure if the copyright is correct as most of the code is from AutoBogus

from: https://www.nuget.org/packages/Soenneker.Utils.AutoBogus

Last but not least, I'm not sure if the name of the forked package will help in making this package a succes. (it contains a username)

PS: there was already a fork (https://www.nuget.org/packages/AutoBogusLifesupport), but the repo's seems to be removed

At the moment internal fields/properties are "ignored", it would be great to give the user of your library the possibility to tell AutoBogus that internal properties/fields should be taken into account as well.

Maybe some kind of global switch (e.g BindingFlags) to enable it if needed.

Br