brazilian-documents-validations 0.0.3

data/.gitignore

@@ -0,0 +1,4 @@
+*.gem
+.bundle
+Gemfile.lock
+pkg/*

data/Gemfile

@@ -0,0 +1,5 @@
+source "http://rubygems.org"
+
+gem 'rails', '3.0.7'
+# Specify your gem's dependencies in brazilian-documents-validations.gemspec
+gemspec

data/Rakefile

@@ -0,0 +1,2 @@
+require 'bundler'
+Bundler::GemHelper.install_tasks

data/brazilian-documents-validations.gemspec

@@ -0,0 +1,23 @@
+# -*- encoding: utf-8 -*-
+$:.push File.expand_path("../lib", __FILE__)
+require "brazilian-documents-validations/version"
+
+Gem::Specification.new do |s|
+  s.name        = "brazilian-documents-validations"
+  s.version     = Brazilian::Documents::Validations::VERSION
+  s.platform    = Gem::Platform::RUBY
+  s.authors     = ["Juan Maiz @joaomilho"]
+  s.email       = ["juanmaiz@gmail.com"]
+  s.homepage    = ""
+  s.summary     = %q{Brazilian Documents Validations}
+  s.description = %q{CPF & CNPJ...}
+  s.add_dependency('rails','3.0.7')
+  # s.add_dependency('rails','3.0.7')
+
+  s.rubyforge_project = "brazilian-documents-validations"
+
+  s.files         = `git ls-files`.split("\n")
+  s.test_files    = `git ls-files -- {test,spec,features}/*`.split("\n")
+  s.executables   = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
+  s.require_paths = ["lib"]
+end

data/lib/brazilian-documents-validations.rb

@@ -0,0 +1,11 @@
+require 'rails'
+require "brazilian-documents-validations/cpf"
+require "brazilian-documents-validations/cnpj"
+class BrazilianDocumentsValidations < Rails::Railtie
+  initializer 'brazilian-documents-validations' do
+    ActiveSupport.on_load :active_record do
+      require "brazilian-documents-validations/cpf_validator"
+      require "brazilian-documents-validations/cnpj_validator"
+    end
+  end
+end

data/lib/brazilian-documents-validations/cnpj.rb

@@ -0,0 +1,46 @@
+module CNPJ
+
+  def self.valid?(cnpj)
+    cnpj = cnpj.to_s
+
+    # could be 13 or 14 digits or with mask 99.999.999/9999-99
+    return false if cnpj !~ /^\d{13,14}|\d{2}\.\d{3}\.\d{3}\/\d{4}-\d{2}$/
+
+
+    cnpj = cnpj.scan(/\d/).collect(&:to_i)
+
+    # filter 111... to 999...
+    return false if cnpj.uniq.size == 1
+
+    cnpj.unshift(0) if cnpj.length == 13
+
+
+    # calculate first digit
+    factor = [5, 4, 3, 2, 9, 8, 7, 6, 5, 4, 3, 2]
+
+    sum = (0..11).inject(0) do |sum, i|
+      sum + cnpj[i] * factor[i]
+    end
+
+    result = sum % 11
+    result = result < 2 ? 0 : 11 - result
+
+    return false if result != cnpj[12]
+
+    # calculate second digit
+    factor.unshift 6
+
+    sum = (0..12).inject(0) do |sum, i|
+      sum + cnpj[i] * factor[i]
+    end
+
+    result = sum % 11
+    result = result < 2 ? 0 : 11 - result
+
+    result == cnpj[13]
+  end
+  
+  def self.invalid?(cnpj)
+    !valid?(cnpj)
+  end
+end

data/lib/brazilian-documents-validations/cnpj_validator.rb

@@ -0,0 +1,5 @@
+class CnpjValidator < ActiveModel::EachValidator
+  def validate_each(record, attribute, value)
+    record.errors.add(attribute, options[:message]) if CNPJ.invalid?(value)
+  end
+end

data/lib/brazilian-documents-validations/cpf.rb

@@ -0,0 +1,58 @@
+module CPF
+
+  BLACK_LIST = (0..9).map{|i| i.to_s * 11 } << '12345678909' unless defined?(BLACK_LIST)
+
+  def self.mock
+    ns = Array.new(9){ (rand*9).round }
+    rec = 10
+    d1 = ns.inject(0){|s,i| s = s + i*rec; rec -= 1; s }
+
+    d1 = 11 - ( d1 % 11 )
+    d1 = 0 if d1 >= 10
+    rec = 11
+    d2 = d1*2 + ns.inject(0){|s,i| s = s + i*rec; rec -= 1; s }
+    d2 = 11 - ( d2 % 11 )
+    d2 = 0 if d2 >= 10
+    ns << d1 << d2
+    ns.join   
+  end
+
+  def self.valid?(cpf)
+    cpf = cpf.to_s
+
+    # could be 10 or 11 digits or with mask 999.999.999-99
+    return false if cpf !~ /^\d{10,11}|\d{3}\.\d{3}\.\d{3}-\d{2}$/
+
+    cpf = cpf.scan(/\d/).collect(&:to_i)
+    cpf.unshift(0) if cpf.length == 10
+
+    # filter black list
+    return false if BLACK_LIST.include? cpf.join
+
+    # calculate first digit
+    sum = (0..8).inject(0) do |sum, i|
+      sum + cpf[i] * (10 - i)
+    end
+
+    result = sum % 11
+    result = result < 2 ? 0 : 11 - result
+
+    return false if result != cpf[9]
+
+    # calculate second digit
+    sum = (0..8).inject(0) do |sum, i|
+      sum + cpf[i] * (11 - i)
+    end
+
+    sum += cpf[9] * 2
+
+    result = sum % 11
+    result = result < 2 ? 0 : 11 - result
+
+    result == cpf[10]
+  end
+
+  def self.invalid?(cpf)
+    !valid?(cpf)
+  end
+end

data/lib/brazilian-documents-validations/cpf_validator.rb

@@ -0,0 +1,5 @@
+class CpfValidator < ActiveModel::EachValidator
+  def validate_each(record, attribute, value)
+    record.errors.add(attribute, options[:message]) if CPF.invalid?(value)
+  end
+end

data/lib/brazilian-documents-validations/version.rb

@@ -0,0 +1,7 @@
+module Brazilian
+  module Documents
+    module Validations
+      VERSION = "0.0.3"
+    end
+  end
+end

data/test-app/.gitignore

@@ -0,0 +1,4 @@
+.bundle
+db/*.sqlite3
+log/*.log
+tmp/

data/test-app/Gemfile

@@ -0,0 +1,9 @@
+source 'http://rubygems.org'
+
+gem 'rails', '3.0.7'
+
+# Bundle edge Rails instead:
+# gem 'rails', :git => 'git://github.com/rails/rails.git'
+
+gem 'sqlite3'
+gem 'brazilian-documents-validations', :path => '../'

data/test-app/README

@@ -0,0 +1,256 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.find(:all)
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.com/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   `-- tasks
+  |-- log
+  |-- public
+  |   |-- images
+  |   |-- javascripts
+  |   `-- stylesheets
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   |-- cache
+  |   |-- pids
+  |   |-- sessions
+  |   `-- sockets
+  `-- vendor
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Contains subdirectories for
+  images, stylesheets, and javascripts. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.