UniqueIndex seems to generate repeating values about bogus HOT 2 CLOSED

You have a Generate(1) that is randomly called call within a rule controlled y.Random.Bool() ? clients.Generate(1).

This is what causes the UniqueIndex to appear to skip values from the outer scope Generate(4). So, the first of Generate(4), may or may not call Generate(1) for a client. If it does call Generate(1) for a client it will cause the UniqueIndex to increment again.

UniqueIndex is not intended to be used or referenced as sequential incrementing value, but more as a globally unique integer that spans the entirety of an app domain and faker instance creations.

If you want to control your own counter (or in this case move sequential across the array of values), you'll have to define and increment your own counter.

Thanks,
Brian

🍂 🍃 Distance - Falling (ft Alys Be)

from bogus.

Hi,

Wouldn't be possible to add to Bogus an, for example, UniqueLocalIndex (or any other name) that would be incremented only in each generation block?

Or maybe a better way to integrate user created indexes in Fluent code of Bogus? Something like:

   int index = 0;
   var users = 
      new Faker<User>()
        .UseIndex(index, 0) // 0 is the initial value. Could be another one.
        .RuleFor(x => x.Name, y => new String[] { "John", "Mary", "Mike", "Tom" }[index % 4])
        .RuleFor(x => x.Email, (y, x) => { return $"{x.Name}@xyz.com".Replace(" ", "").ToLower(); })
        .RuleFor(x => x.Client, y => y.Random.Bool() ? clients.Generate(1).First() : null)
        .RuleFor(x => x.UserName, (y, x) => x.Email)
        .UpdateIndex(index++) // index++ or index = index + 2, etc. index is updated in each cycle. 
        .Generate(4).ToList());

Using Bogus for quite sometime having a local index well integrated is really helpful.
This is very useful when generating data in more complex database models.

Thank You,
Miguel

from bogus.