Open luis-fss opened 8 months ago
If it's of interest, I have made a fork with this feature (and some other changes), at first I didn't intend to create a pull request and the code isn't prepared for that (in fact it's a mess, sorry), but I think it demonstrates my idea in this specific feature.
Do you think it is feasible to add an option to configure a custom username that is different from the email and still unique for each user?
Sure. How do you envision this changing the behavior of Raven.Identity - ID generation being different?
I don't think any changes are necessary in the ID generation, the UserIdType.UserName option already exists.
What I thought is:
Personally, I understand that this can generate too much complexity in the code base, especially in the Create(User)Asyn and Update(User)Asyn methods to ensure that the UserName is unique, but I also think it is a valid feature and use case .
That being said... Of course it's your decision, but don't feel compelled in any way. This project is already quite useful as it is. Thank you.
Do you think it is feasible to add an option to configure a custom username that is different from the email and still unique for each user?
I ask because the user can change their email, but in my use case the username could not be changed and it must be something more concise and shorter than an email.
Thanks.