13 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• David James commented  ·  November 22, 2010 9:22 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  We have ActiveModel in Rails 3. Doesn't it have what this request wants? Let's close this one out.

• kazuyoshi tlacaelel commented  ·  July 17, 2009 10:30 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I agree that model is the driest, if you need too complex validations put them in a mixin or a library and call what you need. I think that integrating validation to the form object is an interesting idea though. but it is kinda that way already if you think of it.

• Nathan Youngman commented  ·  June 2, 2009 12:48 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Having validation down at the model level is great, but I have definitely needed validation for forms that didn't fit that mold (user-created forms). Greater flexibility seems like a necessity when becoming ORM agnostic as well.

  Ideally a nice DRY method for doing both client-side (UJS) and server-side validation for models and any other forms. Django forms may provide inspiration, and apparently DataMapper too.

• eltiare commented  ·  January 21, 2009 3:06 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  FYI You can use DataMapper's validations like that: http://gist.github.com/50106

• eltiare commented  ·  January 21, 2009 3:05 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  As an FYI, you can use DataMapper's validations on any class.

• awattscurnow commented  ·  January 21, 2009 12:33 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Validatable has levels and groups and I wish activerecord had this.

• zdzolton commented  ·  January 12, 2009 7:36 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  +1
  This would help with:
  http://rails.uservoice.com/pages/rails3/suggestions/98492-better-support-for-non-relational-databases

  and, my personal pet:
  http://rails.uservoice.com/pages/rails3/suggestions/98492-better-support-for-non-relational-databases

• Soleone commented  ·  January 9, 2009 7:06 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  Sounds really like an interesting and useful idea to me. Maybe create something like ActiveModel with no DB backend (as a Mixin) or somehow else get the validators in the forms.

• konstantin.k commented  ·  January 9, 2009 12:50 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I think the "dryest" place for Validation is in the model and i think theres no need to make it more complex. but if the validators would be more modular to include and use them in any class in apps/model

• kakutani commented  ·  January 7, 2009 1:54 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I'd like to use validation with ActivePresenter.

• cheapRoc commented  ·  January 6, 2009 7:15 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  validatable gem FTW

• a_matsuda commented  ·  January 5, 2009 8:25 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  ActiveModel! ActiveModel!!

• randlaeufer commented  ·  January 5, 2009 2:44 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  How is this not on the top of the list?