Add uniqueness to certain random values about falso

[NetanelBasal]

Any reason you're not using seed?

https://github.com/ngneat/falso#setting-a-randomness-seed

[rijkvanzanten]

@NetanelBasal I don't think that fully solves this particular issue does it? It allows repeat tests to get the same values back every time, but it doesn't insure that those individual values are unique from each other in the first place. If I were to rely on seeds as a solution for this, I'd have to go through a number of seeds first to find one that returns unique values, and then use that, whereas I'm hoping randFilePath() could return a unique path regardless of seed used.

[NetanelBasal]

Can you create a small stackblitz that explains your point, please?

[rijkvanzanten]

The smallest explanation I have is:

import { randFilePath } from '@ngneat/falso';

const path1 = randFilePath();
const path2 = randFilePath();

path1 === path2; // This is sometimes true, should always be false

[PumpedSardines]

Not sure I agree that randFilePath always should be different, randomness can be the same sometimes. However randFilePath is rather lacking in the amount of return values. There should definitely be a less than 1 in a 100 chance to get the same output.

For your particular case I would just use seed like @NetanelBasal suggested, however I do realise it's unsatisfying.

The question of uniqueness was discussed briefly in #220, but the solution there seemed rather strange imho.

[NetanelBasal]

Agree with @PumpedSardines that randomness can be the same sometimes.

[rijkvanzanten]

OK! Whatever you guys prefer. For my use cases, the high chance of collision is a big hindrance, so I'll rely on an alternative approach 👍🏻