Code Monkey home page Code Monkey logo

grouped_validations's Introduction

Grouped Validations

Allows you to define ActiveModel validation groups for more control over what validations you want to run.

This can be useful for multi-page forms or wizard style data entry.

Works with Rails 3.

For Rails 2.x support, try version 0.2.2.

Installation

Just install the gem

gem install grouped_validations

Add it to your Rails environment gems

config.gem 'grouped_validations'

Usage

Define validations as you would normally but inside a validation_group block which you pass a group name to.

class Person < ActiveRecord::Base
  validation_group :name do
    validates_presence_of :first_name
    validates_presence_of :last_name
  end

  validates_presence_of :sex
end

You can define validations outside the group as normal.

To check for errors for only a certain group of validations

p = Person.new
p.group_valid?(:name) # => false
p.first_name = 'John'
p.last_name = 'Smith'
p.group_valid?(:name) # => true

If you run the normal valid? method all validations, inside and outside validation groups, will be run.

p.valid? # => false because sex is not present

You can also check validation for multiple groups

p.groups_valid?(:group1, :group2)

To define validation blocks just use the respective group validation method, like so

class Person < ActiveRecord::Base
  validation_group :name do
    validates_presence_of :first_name
    validates_presence_of :last_name
  end

  validate_name           {|r| # something custom on save }
  validate_name_on_create {|r| # something custom on create }
  validate_name_on_update {|r| # something custom on update }
end

Group Options

You can use a validation group like similar to the with_options method, but for validation methods only.

If you pass in an options hash, those options will be applied to each valiation method in the block.

validation_group :name, :if => :ready? do
  validates_presence_of :first_name
  validates_presence_of :last_name
end

Which effectively the same as doing the following:

validates_presence_of :first_name, :if => :ready?
validates_presence_of :last_name, :if => :ready?

If you set an option for a specific validation method, it will not be overriden with the validation group options.

validation_group :name, :if => :ready? do
  validates_presence_of :first_name
  validates_presence_of :last_name, :if => {|r| !r.popstar? }
end

The last_name attribute will be required unless the person is a popstar.

The options should work for any validation method which calls the validate class method internally. This includes all the default validations.

For more precision on when to merge the groups options you can pass an argument to the block and use it like a with_options call. Then only those validation methods call on the argument will have the options merged in.

validation_group :name, :if => :ready? do |options|
  # Options merged
  options.validates_presence_of :first_name

  # No options merged
  validates_presence_of :last_name
end

Grouped Errors

The errors for the model can be returned as hash with the group names as the keys. If you have a number of groups you can deal with the error messages in specific ways per group.

validation_group :name do
  validates_presence_of :first_name
  validates_presence_of :last_name
end

validates_presence_of :sex

To access all errors outside of a validation group, use nil as the key:

person.grouped_errors[nil]

Use the group name as the key for all errors in that group:

person.grouped_errors[:name]

Be aware that the validations will all be run. If you have just called valid? then the same validations will be run again and the current state of the object is used. This is for consideration if the validations are expensive, time sensitive or you have changed the object after calling valid?.

You can use the grouped_errors method instead of valid? to check on a valid object like so:

# Validations all run
if person.grouped_errors.empty?
  # object is valid
end

Credits

Copyright © 2010-2011 Adam Meehan, released under the MIT license

grouped_validations's People

Contributors

adzap avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

grouped_validations's Issues

Validation group with options throws ArgumentError

Passing a condition for the options argument results in an ArgumentError (wrong number of arguments (2 for 1)). This happens on Rails 3.0.5, using v0.2.2 of the gem.

validation_group :address, :if => address_required? do
    validates :address, :postal_number, :postal_address, :presence => true
end

def address_required?
    true
end

Rails 4 undefined method `_run_validate_#{group}_callbacks' for #<Quote:0x00000101da89a8>

Rails 4.0.1
Ruby 2.0.0-p247

I defined a group called :offer in my Quote model.

validation_group :offer do
validates_presence_of :initials
end

When I start the console and test the following:

[1] pry(main)> q = Quote.new
[2] pry(main)> q.valid?
NoMethodError: undefined method _run_validate_offer_callbacks' for #<Quote:0x00000101da89a8> from /Users/peter/.rvm/gems/ruby-2.0.0-p247/gems/activemodel-4.0.1/lib/active_model/attribute_methods.rb:439:inmethod_missing'

Same happens for q.groups_valid?(:offer)

I noticed that it works when you replace:
send(:"_run_validate_#{group}_callbacks")
with:
run_callbacks(:"validate_#{group}")

But I don't know if it's the proper way.

documentation needs update

Currently, the last bit of the Usage section reads:

To define validation blocks just use the respective group validation method, like so

class Person < ActiveRecord::Base
  validation_group :name do
     validates_presence_of :first_name
     validates_presence_of :last_name
  end

  validate_name           {|r| # something custom on save }
  validate_name_on_create {|r| # something custom on create }
  validate_name_on_update {|r| # something custom on update }
end

But unless I am seriously mistaken, it should be more like:

To define validation blocks just include a custom 'validate' method within the validation group, like so

class Person < ActiveRecord::Base
  validation_group :name do
    validates_presence_of :first_name
    validates_presence_of :last_name
    validate           {|r| # something custom on save }
    validate_on_create {|r| # something custom on create }
    validate_on_update {|r| # something custom on update }
  end
end

License missing from gemspec

RubyGems.org doesn't report a license for your gem. This is because it is not specified in the gemspec of your last release.

via e.g.

spec.license = 'MIT'
# or
spec.licenses = ['MIT', 'GPL-2']

Including a license in your gemspec is an easy way for rubygems.org and other tools to check how your gem is licensed. As you can imagine, scanning your repository for a LICENSE file or parsing the README, and then attempting to identify the license or licenses is much more difficult and more error prone. So, even for projects that already specify a license, including a license in your gemspec is a good practice. See, for example, how rubygems.org uses the gemspec to display the rails gem license.

There is even a License Finder gem to help companies/individuals ensure all gems they use meet their licensing needs. This tool depends on license information being available in the gemspec. This is an important enough issue that even Bundler now generates gems with a default 'MIT' license.

I hope you'll consider specifying a license in your gemspec. If not, please just close the issue with a nice message. In either case, I'll follow up. Thanks for your time!

Appendix:

If you need help choosing a license (sorry, I haven't checked your readme or looked for a license file), GitHub has created a license picker tool. Code without a license specified defaults to 'All rights reserved'-- denying others all rights to use of the code.
Here's a list of the license names I've found and their frequencies

p.s. In case you're wondering how I found you and why I made this issue, it's because I'm collecting stats on gems (I was originally looking for download data) and decided to collect license metadata,too, and make issues for gemspecs not specifying a license as a public service :). See the previous link or my blog post about this project for more information.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.