email_attribute 0.0.1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 6475956485450992d727a73323178a70d7c04151
+  data.tar.gz: c10646c378fc05604a6f178afe896f7c534cea8c
+SHA512:
+  metadata.gz: 96c93d3e9e28e0a38d593fd2bb7ff78f8e377d6ac5a21cfe6e6d1e02e00ad5adf3f049e8e348fdeff6df0d37f4496c7e1b7528e2d4ac0cda08acc480b4e6b569
+  data.tar.gz: 11efdb77151cd4c5528ac20007e6b04e69efb7f72d0c1a7335ddccb0ebc3e208b60cdf697b643a92157aa7f6fd6c2456cd1039a7ded183d358949ecedbf6c7c8

data/MIT-LICENSE

@@ -0,0 +1,20 @@
+Copyright 2013 YOURNAME
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,78 @@
+# EmailAttribute [![Build Status](https://travis-ci.org/chingor13/email_attribute.png)](https://travis-ci.org/chingor13/email_attribute)
+
+ActiveModel attribute serialization using the `mail` gem.
+
+## Usage
+
+Assuming you have a column named `address` on the `email_addresses` table, you can easily add email address handling with:
+
+```
+class EmailAddresses < ActiveRecord::Base
+  email_address_attribute :address
+end
+
+email = EmailAddress.new({
+  address: "Jeff Ching <ching.jeff@gmail.com>"
+})
+
+email.address
+=> "Jeff Ching <ching.jeff@gmail.com>"
+
+email.address = "ching.jeff@gmail.com"
+email.address
+=> "ching.jeff@gmail.com"
+
+email.address = "some bad email address"
+email.address
+=> "some bad email address"
+```
+
+You can also specify a column as a email address list type, which is a serialized array of email addresses.
+
+```
+class Email < ActiveRecord::Base
+  email_address_list_attribute :to
+end
+
+email = Email.new({
+  to: "Jeff Ching <ching.jeff@gmail.com>; email@foo.com"
+})
+email.to
+=> "Jeff Ching <ching.jeff@gmail.com>; email@foo.com"
+
+email.to.length 
+=> 2
+
+```
+
+## Validating
+
+`EmailAttribute` provides validation to `ActiveModel`.  To use:
+
+```
+class EmailAddresses < ActiveRecord::Base
+  email_address_attribute :address
+  validates :address, email: { 
+    allow_blank: true,
+    message: "is invalid"
+  }
+end
+
+email = EmailAddress.new({
+  address: "some bad email address"
+})
+email.save
+=> false
+
+email.errors.full_messages
+=> ["Address is invalid"]
+```
+
+## Formatting
+
+`PhonyAttribute` comes built with a few named formats. You can add your own by adding to the `PhonyAttribute::PhoneNumber.named_formats` hash.  The value can be either an options hash (passed directly to Phony's format) or a callable Proc/lambda that yields the phone number object.
+
+
+## License
+
+This project rocks and uses MIT-LICENSE.

data/Rakefile

@@ -0,0 +1,38 @@
+#!/usr/bin/env rake
+begin
+  require 'bundler/setup'
+rescue LoadError
+  puts 'You must `gem install bundler` and `bundle install` to run rake tasks'
+end
+begin
+  require 'rdoc/task'
+rescue LoadError
+  require 'rdoc/rdoc'
+  require 'rake/rdoctask'
+  RDoc::Task = Rake::RDocTask
+end
+
+RDoc::Task.new(:rdoc) do |rdoc|
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title    = 'EmailAttribute'
+  rdoc.options << '--line-numbers'
+  rdoc.rdoc_files.include('README.rdoc')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end
+
+
+
+
+Bundler::GemHelper.install_tasks
+
+require 'rake/testtask'
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << 'lib'
+  t.libs << 'test'
+  t.pattern = 'test/**/*_test.rb'
+  t.verbose = false
+end
+
+
+task :default => :test

data/lib/email_attribute/attribute.rb

@@ -0,0 +1,40 @@
+module EmailAttribute
+  module Attribute
+    extend ActiveSupport::Concern
+
+    module ClassMethods
+      def email_address_list_attribute(*attributes)
+        options = attributes.extract_options!
+
+        attributes.each do |attribute|
+          serialize attribute, EmailAttribute::List
+
+          method_body, line = <<-EOV, __LINE__ + 1
+            def #{attribute}=(email_address)
+              list = EmailAttribute::List.new(email_address) rescue email_address
+              write_attribute(:#{attribute}, list)
+            end
+          EOV
+
+          class_eval method_body, __FILE__, line
+        end
+      end
+
+      def email_address_attribute(*attributes)
+        options = attributes.extract_options!
+
+        attributes.each do |attribute|
+          serialize attribute, EmailAttribute::SingleAddress
+
+          method_body, line = <<-EOV, __LINE__ + 1
+            def #{attribute}=(email_address)
+              write_attribute(:#{attribute}, EmailAttribute::SingleAddress.new(email_address))
+            end
+          EOV
+
+          class_eval method_body, __FILE__, line
+        end
+      end
+    end
+  end
+end

data/lib/email_attribute/email_validator.rb

@@ -0,0 +1,30 @@
+# global namespace so you can use the rails 3 "validate :field, email: [options]"
+class EmailValidator < ActiveModel::EachValidator
+  def validate_each(record,attribute,value)
+    return if value.blank? && options[:allow_blank]
+
+    case value
+    when EmailAttribute::SingleAddress
+      validate_single_address_model(record, attribute, value.address)
+    when String
+      validate_single_address_model(record, attribute, value)
+    when EmailAttribute::List
+      value.each do |address|
+        validate_single_address_model(record, attribute, address)
+      end
+    end
+  end
+
+  protected
+
+  # model should be a Mail::Address model
+  def validate_single_address_model(record, attribute, model)
+    begin
+      model = EmailAttribute::SingleAddress.new(model).address if model.is_a?(String)
+      r = model.domain && model.domain.split(".").length > 1
+    rescue Exception => e
+      r = false
+    end
+    record.errors.add(attribute, (options[:message] || :invalid)) unless r
+  end
+end

data/lib/email_attribute/list.rb

@@ -0,0 +1,57 @@
+module EmailAttribute
+  # serializeable model that wraps Mail::AddressList
+  class List
+    attr_reader :addresses
+    delegate :length, :size, :each, :to => :addresses
+
+    def initialize(email_addresses)
+      email_addresses = email_addresses.join(", ") if email_addresses.respond_to?(:join)
+      @addresses = begin
+        Mail::AddressList.new(email_addresses).addresses.map(&:format)
+      rescue
+        manual_parse(email_addresses)
+      end
+    end
+
+    def inspect
+      to_s
+    end
+
+    def to_s
+      addresses.join(", ")
+    end
+
+    def present?
+      length > 0
+    end
+
+    def blank?
+      !present?
+    end
+
+    def strip
+      to_s.strip
+    end
+
+    class << self
+      def dump(email_address)
+        return nil if email_address.nil?
+
+        email_address.to_s
+      end
+
+      def load(email_address)
+        new(email_address)
+      end
+    end
+
+    protected
+
+    def manual_parse(email_addresses)
+      email_addresses.split(/[,;]/).map do |address|
+        Mail::Address.new(address).format rescue address
+      end
+    end
+  end
+
+end

data/lib/email_attribute/railtie.rb

@@ -0,0 +1,12 @@
+module EmailAttribute
+  class Railtie < ::Rails::Railtie
+
+    initializer "email_attribute" do
+      require 'email_attribute/email_validator'
+      ActiveSupport.on_load :active_record do
+        include EmailAttribute::Attribute
+      end
+    end
+
+  end
+end

data/lib/email_attribute/single_address.rb

@@ -0,0 +1,31 @@
+module EmailAttribute
+  class SingleAddress < String
+    def initialize(str = "")
+      @address = Mail::Address.new(str.to_s) rescue nil
+      if @address
+        value = @address.format
+      else
+        value = str || ""
+      end
+      super(value)
+    end
+
+    # rebuilds the Mail::Address if necessary
+    # using string methods on this object can bypass the initializer
+    def address
+      @address ||= Mail::Address.new(self.to_s) rescue nil
+    end
+
+    class << self
+      def dump(email_address)
+        return nil if email_address.nil?
+
+        email_address.to_s
+      end
+
+      def load(email_address)
+        new(email_address)
+      end
+    end
+  end
+end

data/lib/email_attribute/version.rb

@@ -0,0 +1,3 @@
+module EmailAttribute
+  VERSION = "0.0.1"
+end

data/lib/email_attribute.rb

@@ -0,0 +1,9 @@
+require 'mail'
+
+module EmailAttribute
+  autoload :Attribute, "email_attribute/attribute"
+  autoload :List, "email_attribute/list"
+  autoload :SingleAddress, "email_attribute/single_address"
+end
+
+require 'email_attribute/railtie'

data/lib/tasks/email_attribute_tasks.rake

@@ -0,0 +1,4 @@
+# desc "Explaining what the task does"
+# task :email_attribute do
+#   # Task goes here
+# end

data/test/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== 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.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.org/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
+  |   |-- assets
+  |   |   |-- images
+  |   |   |-- javascripts
+  |   |   `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   |-- assets
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   `-- cache
+  |       `-- assets
+  `-- vendor
+      |-- assets
+      |   |-- javascripts
+      |   `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+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. 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.

data/test/dummy/Rakefile

@@ -0,0 +1,7 @@
+#!/usr/bin/env rake
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+
+require File.expand_path('../config/application', __FILE__)
+
+Dummy::Application.load_tasks

data/test/dummy/app/assets/javascripts/application.js

@@ -0,0 +1,15 @@
+// This is a manifest file that'll be compiled into application.js, which will include all the files
+// listed below.
+//
+// Any JavaScript/Coffee file within this directory, lib/assets/javascripts, vendor/assets/javascripts,
+// or vendor/assets/javascripts of plugins, if any, can be referenced here using a relative path.
+//
+// It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the
+// the compiled file.
+//
+// WARNING: THE FIRST BLANK LINE MARKS THE END OF WHAT'S TO BE PROCESSED, ANY BLANK LINE SHOULD
+// GO AFTER THE REQUIRES BELOW.
+//
+//= require jquery
+//= require jquery_ujs
+//= require_tree .

data/test/dummy/app/assets/stylesheets/application.css

@@ -0,0 +1,13 @@
+/*
+ * This is a manifest file that'll be compiled into application.css, which will include all the files
+ * listed below.
+ *
+ * Any CSS and SCSS file within this directory, lib/assets/stylesheets, vendor/assets/stylesheets,
+ * or vendor/assets/stylesheets of plugins, if any, can be referenced here using a relative path.
+ *
+ * You're free to add application-wide styles to this file and they'll appear at the top of the
+ * compiled file, but it's generally better to create a new file per style scope.
+ *
+ *= require_self
+ *= require_tree .
+ */

data/test/dummy/app/controllers/application_controller.rb

@@ -0,0 +1,3 @@
+class ApplicationController < ActionController::Base
+  protect_from_forgery
+end

data/test/dummy/app/helpers/application_helper.rb

@@ -0,0 +1,2 @@
+module ApplicationHelper
+end

data/test/dummy/app/models/email.rb

@@ -0,0 +1,11 @@
+class Email < ActiveRecord::Base
+
+  email_address_attribute :from
+  email_address_list_attribute :to
+
+  validates :from, email: {message: "custom message"}
+  validates :to, email: {message: "another message"}
+
+  validates :subject, :body, presence: true
+
+end

data/test/dummy/app/views/layouts/application.html.erb

@@ -0,0 +1,14 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <title>Dummy</title>
+  <%= stylesheet_link_tag    "application", :media => "all" %>
+  <%= javascript_include_tag "application" %>
+  <%= csrf_meta_tags %>
+</head>
+<body>
+
+<%= yield %>
+
+</body>
+</html>