You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@clement128 good idea, but I decided to go with a dedicated exception type. Mainly because I did not want to break backwards compatibility with this project in my fork.
I actually don't see why you could not guarantee password generation with every call. you might need to tweak the algorithm but I really cannot fathom any reason why it would not be possible... :/
Can the call to
.Next()
throw instead of returning a password called "Try again" when a valid password could not be generated inmaximumAttempts
?I think it's a big risk to return a string like that as the calling application has no way to know what was returned is not a valid password.
A dedicated exception type would be a bonus.
Source
The text was updated successfully, but these errors were encountered: