Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

client_side_validation and Omniauth-identity #17

Open
seivan opened this issue Feb 5, 2012 · 1 comment
Open

client_side_validation and Omniauth-identity #17

seivan opened this issue Feb 5, 2012 · 1 comment
Assignees

Comments

@seivan
Copy link

seivan commented Feb 5, 2012

So, here is the deal, client_side_validation gem requires params to be nested in order to work fully out of the box with uniqueness validation. Also that's proper Rails convention to usually have nested params under a class/model name.

So, how about allowing that in the initializer?

:identity => {:email => .... , :password => "....}

Example application
https://github.com/seivan/simple_form_2_client_side_validation_example

@pboling
Copy link
Member

pboling commented Feb 14, 2021

This would be cool. Leaving this open to investigate.

@pboling pboling self-assigned this Feb 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants