challah 1.0.0.beta3 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: a4d3a330bc6bf33367b6f7d6e21d60d4907d72c3
-  data.tar.gz: feab5516162daa12bfef57749eed02a80d1f37e5
+  metadata.gz: de60f1578f04cfcff49e06a36dacdf94601198bd
+  data.tar.gz: c733d09838206401b8328635a7ecbea2f09ebc44
 SHA512:
-  metadata.gz: 64c62fca6eb6b5fd7c12b7ccf47c0080246929517193327c950696a94b13ee4909a82e0465607442bd094a9b11848e36a5c2bc2d25137696bbb6ad5d2de230bc
-  data.tar.gz: b5aae4f070b0eab4531b96d4a18cb44b393c5db4e02ad0caf1635ce1e2d36c095a4a3e87a85661e9ac7ae1fd4923f11cb054b1f9565d7e02f5ecdc39f27e4108
+  metadata.gz: d430ba2a8af1d847de71b1ce169e691bb9d8c7602dd99708d8db83f296b9b651637ae071a938e251a158a2d4462610d151dde4a8a195ceebb93303e73fed21c6
+  data.tar.gz: 0928d0c628b46a3e569650a931a92a713bb558da79d0c9595158440bbfb68504992eeda7637cc6726b5518579f939036ee384a583f0070ed15840e12dda06935

data/CHANGELOG.md

@@ -1,8 +1,8 @@
-## Challah 1.0.0.beta
+## Challah 1.0.0
 
 * Ruby 2.0 compatibility
 * Add option to disable built-in validations
-* Rails 4.0.0 beta support, use lambdas for model scopes
+* Rails 4.0.0 is the only supported Rails version
 
 ## Challah 0.9.1
 

data/lib/challah/user.rb

@@ -30,11 +30,6 @@ module Challah
 
         attr_reader :password, :password_confirmation, :password_updated
 
-        # Kind of hacky, is there a better way to do this?
-        if Rails::VERSION::MAJOR < 4
-          attr_accessible :provider_attributes
-        end
-
         # Validation
         ################################################################
 

data/lib/challah/version.rb

@@ -1,3 +1,3 @@
 module Challah
-  VERSION = "1.0.0.beta3" unless defined?(::Challah::VERSION)
+  VERSION = "1.0.0" unless defined?(::Challah::VERSION)
 end

data/test/helper.rb

@@ -4,7 +4,7 @@ require 'simplecov'
 # Setup a sample rails app for testing rails modules
 sample_root = File.expand_path(File.join(File.dirname(__FILE__), '..', 'tmp', 'sampleapp'))
 FileUtils.rm_rf(sample_root) if File.exists?(sample_root)
-`rails new #{sample_root} --skip-bundle --skip-sprockets`
+`./bin/rails new #{sample_root} --skip-bundle --skip-sprockets`
 
 # Setup environment variables for the Rails instance
 ENV['RAILS_ENV'] = 'test'

data/vendor/bundle/gems/actionmailer-4.0.0/CHANGELOG.md

@@ -0,0 +1,59 @@
+## Rails 4.0.0 (June 25, 2013) ##
+
+*   Allow passing interpolations to `#default_i18n_subject`, e.g.:
+
+        # config/locales/en.yml
+        en:
+          user_mailer:
+            welcome:
+              subject: 'Hello, %{username}'
+
+        # app/mailers/user_mailer.rb
+        class UserMailer < ActionMailer::Base
+          def welcome(user)
+            mail(subject: default_i18n_subject(username: user.name))
+          end
+        end
+
+    *Olek Janiszewski*
+
+*   Eager loading made to use relation's `in_clause_length` instead of host's one.
+    Fixes #8474.
+
+    *Boris Staal*
+
+*   Explicit multipart messages no longer set the order of the MIME parts.
+
+    *Nate Berkopec*
+
+*   Do not render views when `mail` isn't called. Fixes #7761.
+
+    *Yves Senn*
+
+*   Allow delivery method options to be set per mail instance.
+
+    If your SMTP delivery settings are dynamic, you can now override settings
+    per mail instance for e.g.
+
+        def my_mailer(user, company)
+          mail to: user.email, subject: "Welcome!",
+               delivery_method_options: { user_name: company.smtp_user,
+                                          password: company.smtp_password }
+        end
+
+    This will ensure that your default SMTP settings will be overridden
+    by the company specific ones. You only have to override the settings
+    that are dynamic and leave the static setting in your environment
+    configuration file (e.g. `config/environments/production.rb`).
+
+    *Aditya Sanghi*
+
+*   Allow to set default Action Mailer options via `config.action_mailer.default_options=`. *Robert Pankowecki*
+
+*   Raise an `ActionView::MissingTemplate` exception when no implicit template could be found. *Damien Mathieu*
+
+*   Allow callbacks to be defined in mailers similar to `ActionController::Base`. You can configure default
+    settings, headers, attachments, delivery settings or change delivery using
+    `before_filter`, `after_filter`, etc. *Justin S. Leitgeb*
+
+Please check [3-2-stable](https://github.com/rails/rails/blob/3-2-stable/actionmailer/CHANGELOG.md) for previous changes.

data/vendor/bundle/gems/actionmailer-4.0.0/MIT-LICENSE

@@ -0,0 +1,21 @@
+Copyright (c) 2004-2013 David Heinemeier Hansson
+
+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/vendor/bundle/gems/actionmailer-4.0.0/README.rdoc

@@ -0,0 +1,164 @@
+= Action Mailer -- Easy email delivery and testing
+
+Action Mailer is a framework for designing email service layers. These layers
+are used to consolidate code for sending out forgotten passwords, welcome
+wishes on signup, invoices for billing, and any other use case that requires
+a written notification to either a person or another system.
+
+Action Mailer is in essence a wrapper around Action Controller and the
+Mail gem.  It provides a way to make emails using templates in the same
+way that Action Controller renders views using templates.
+
+Additionally, an Action Mailer class can be used to process incoming email,
+such as allowing a blog to accept new posts from an email (which could even
+have been sent from a phone).
+
+== Sending emails
+
+The framework works by initializing any instance variables you want to be
+available in the email template, followed by a call to +mail+ to deliver
+the email.
+
+This can be as simple as:
+
+  class Notifier < ActionMailer::Base
+    default from: 'system@loudthinking.com'
+
+    def welcome(recipient)
+      @recipient = recipient
+      mail(to: recipient,
+           subject: "[Signed up] Welcome #{recipient}")
+    end
+  end
+
+The body of the email is created by using an Action View template (regular
+ERB) that has the instance variables that are declared in the mailer action.
+
+So the corresponding body template for the method above could look like this:
+
+  Hello there,
+
+  Mr. <%= @recipient %>
+
+  Thank you for signing up!
+
+If the recipient was given as "david@loudthinking.com", the email
+generated would look like this:
+
+  Date: Mon, 25 Jan 2010 22:48:09 +1100
+  From: system@loudthinking.com
+  To: david@loudthinking.com
+  Message-ID: <4b5d84f9dd6a5_7380800b81ac29578@void.loudthinking.com.mail>
+  Subject: [Signed up] Welcome david@loudthinking.com
+  Mime-Version: 1.0
+  Content-Type: text/plain;
+  	charset="US-ASCII";
+  Content-Transfer-Encoding: 7bit
+
+  Hello there,
+
+  Mr. david@loudthinking.com
+
+  Thank you for signing up!
+
+In previous version of Rails you would call <tt>create_method_name</tt> and
+<tt>deliver_method_name</tt>.  Rails 3.0 has a much simpler interface - you
+simply call the method and optionally call +deliver+ on the return value.
+
+Calling the method returns a Mail Message object:
+
+  message = Notifier.welcome("david@loudthinking.com")  # => Returns a Mail::Message object
+  message.deliver                                       # => delivers the email
+
+Or you can just chain the methods together like:
+
+  Notifier.welcome("david@loudthinking.com").deliver    # Creates the email and sends it immediately
+
+== Setting defaults
+
+It is possible to set default values that will be used in every method in your Action Mailer class. To implement this functionality, you just call the public class method <tt>default</tt> which you get for free from ActionMailer::Base. This method accepts a Hash as the parameter. You can use any of the headers e-mail messages has, like <tt>:from</tt> as the key. You can also pass in a string as the key, like "Content-Type", but Action Mailer does this out of the box for you, so you won't need to worry about that. Finally, it is also possible to pass in a Proc that will get evaluated when it is needed.
+
+Note that every value you set with this method will get overwritten if you use the same key in your mailer method.
+
+Example:
+
+  class AuthenticationMailer < ActionMailer::Base
+    default from: "awesome@application.com", subject: Proc.new { "E-mail was generated at #{Time.now}" }
+    .....
+  end
+
+== Receiving emails
+
+To receive emails, you need to implement a public instance method called <tt>receive</tt> that takes an
+email object as its single parameter. The Action Mailer framework has a corresponding class method,
+which is also called <tt>receive</tt>, that accepts a raw, unprocessed email as a string, which it then turns
+into the email object and calls the receive instance method.
+
+Example:
+
+  class Mailman < ActionMailer::Base
+    def receive(email)
+      page = Page.find_by(address: email.to.first)
+      page.emails.create(
+        subject: email.subject, body: email.body
+      )
+
+      if email.has_attachments?
+        email.attachments.each do |attachment| 
+          page.attachments.create({
+            file: attachment, description: email.subject
+          })
+        end
+      end
+    end
+  end
+
+This Mailman can be the target for Postfix or other MTAs. In Rails, you would use the runner in the
+trivial case like this:
+
+  rails runner 'Mailman.receive(STDIN.read)'
+
+However, invoking Rails in the runner for each mail to be received is very resource intensive.  A single
+instance of Rails should be run within a daemon, if it is going to process more than just a limited amount of email.
+
+== Configuration
+
+The Base class has the full list of configuration options. Here's an example:
+
+  ActionMailer::Base.smtp_settings = {
+    address:        'smtp.yourserver.com', # default: localhost
+    port:           '25',                  # default: 25
+    user_name:      'user',
+    password:       'pass',
+    authentication: :plain                 # :plain, :login or :cram_md5
+  }
+
+
+== Download and installation
+
+The latest version of Action Mailer can be installed with RubyGems:
+
+  % [sudo] gem install actionmailer
+
+Source code can be downloaded as part of the Rails project on GitHub
+
+* https://github.com/rails/rails/tree/master/actionmailer
+
+
+== License
+
+Action Mailer is released under the MIT license:
+
+* http://www.opensource.org/licenses/MIT
+
+
+== Support
+
+API documentation is at
+
+* http://api.rubyonrails.org
+
+Bug reports and feature requests can be filed with the rest for the Ruby on Rails project here:
+
+* https://github.com/rails/rails/issues
+

data/vendor/bundle/gems/actionmailer-4.0.0/lib/action_mailer.rb

@@ -0,0 +1,47 @@
+#--
+# Copyright (c) 2004-2013 David Heinemeier Hansson
+#
+# 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.
+#++
+
+require 'abstract_controller'
+require 'action_view'
+require 'action_mailer/version'
+
+# Common Active Support usage in Action Mailer
+require 'active_support/rails'
+require 'active_support/core_ext/class'
+require 'active_support/core_ext/module/attr_internal'
+require 'active_support/core_ext/string/inflections'
+require 'active_support/lazy_load_hooks'
+
+module ActionMailer
+  extend ::ActiveSupport::Autoload
+
+  eager_autoload do
+    autoload :Collector
+  end
+
+  autoload :Base
+  autoload :DeliveryMethods
+  autoload :MailHelper
+  autoload :TestCase
+  autoload :TestHelper
+end