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
{{ message }}
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.
It's a bit cumbersome to allow users to enter whatever they want in the signup form, just to tell them they did it wrong afterwards. We should perform some client side checks (e.g. format of the username, that both the confirmation and the password match, etc.), and disallow the creation of the user if the requirements are not met.
Update
Provide a /validate API endpoint for this resource.
Add the necessary client-side work.
The text was updated successfully, but these errors were encountered:
One of the full time engineer from Suse let me to this project to help and also learn, knowing how i reach this project want to know how can i contribute with you guys?
Should we use the client_side_validation gem for this purpose or have a custom implementation for that. I am interested in doing this fix. Please help me in this regard. And what do we mean by the format of username exactly? I mean is there any predefined format for that.
@krishnak9 this gem looks unnecessary. That being said, I'm not entirely sure what would be the best way to handle this. You could either do some validation entirely on the client side, or add a method on the registrations controller that the client code can call.
It's a bit cumbersome to allow users to enter whatever they want in the signup form, just to tell them they did it wrong afterwards. We should perform some client side checks (e.g. format of the
username
, that both the confirmation and the password match, etc.), and disallow the creation of the user if the requirements are not met.Update
/validate
API endpoint for this resource.The text was updated successfully, but these errors were encountered: