devise-multi_email 1.0.5 → 2.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 761e1bd9778356e36ea03f9e3e6d1b52acb11aea
-  data.tar.gz: 14dc6f85dee81396aef5794575b6b27dff79ab3d
+  metadata.gz: ae0a4824abdf90e63b3a5027520c2d4ef6465e31
+  data.tar.gz: ae37353431e7e16eb565a0ba27c814020f644f3e
 SHA512:
-  metadata.gz: 4bc72f639a6dd6503aa415901a09bd47a512f3a63f822111b91fc50688cf32226e01e8942e9cbf1f31314c376496cf6cd608c725cff02a7284b5703cb96ebae9
-  data.tar.gz: '08d80d91add8d86df88ba7b671829ce783850f17dd1fd2539d06d43b3709e7fa7b079873f0b64a5aa5bea291943f924e18bb98ed445384872a5fddc9ba2c4a69'
+  metadata.gz: 232a734290ad0eab39000b8ecb76a3c6fc320ece267fdd43a52a1dadf726ee50cd97dae4c712de750a757ca48bbf72e9b7d6fc59b3e138b32414ee6b9d915e06
+  data.tar.gz: 658d6b2220f1eaf9ca811d4df1b669a938cb7a2911c803abc5546eec9def051756511228eff406b282d7e088084fd8610b7950b88f6d71f2ded2876a187e59f2

data/.travis.yml

@@ -1,5 +1,8 @@
 language: ruby
 rvm:
-  - 2.3.0
   - 2.3.1
+  - 2.4.1
+gemfile:
+  - gemfiles/rails_5_0.gemfile
+  - gemfiles/rails_4_2.gemfile
 before_install: gem install bundler -v 1.10.6

data/CHANGELOG.md

@@ -1,12 +1,25 @@
+### 2.0.0 - 2017-05-12
+
+* New `Devise::MultiEmail#configure` setup with options for `user` and `emails` associations and `primary_email` method names
+* Refactor to expose `_multi_email_*` prefixed methods on models
+* New `primary_email` method to get primary email record (however, can be configured as `primary_email_record` for backwards-compatibility)
+* Changed logic when changing an email address to look up existing email record, otherwise creating a new one, then marking it "primary"
+* Changed logic when changing an email address to mark all others as `primary = false`
+* Changed logic when changing an email address to `nil` to mark as `primary = false` rather than deleting records
+
+Many thanks to [joelvh](https://github.com/joelvh) for the great work!
+
 ### 1.0.5 - 2016-12-29
-* New `.find_by_email` method. Thanks to [mrjlynch](https://github.com/mrjlynch). 
+
+* New `.find_by_email` method. Thanks to [mrjlynch](https://github.com/mrjlynch).
 
 ### 1.0.4 - 2016-08-13
+
 * Bug fix: Case-insentive configuration of email is ignored (#1). Thanks to [@fonglh](https://github.com/fonglh).
 
 ### 1.0.3 - 2016-02-18
 
-* Bug fix: Fix a wrong error message which shows "Email can't be blank" when email does not exist. 
+* Bug fix: Fix a wrong error message which shows "Email can't be blank" when email does not exist.
 
 ### 1.0.2 - 2016-01-12
 

data/Gemfile

@@ -1,14 +1,7 @@
 source 'https://rubygems.org'
 
-# Specify your gem's dependencies in devise-multi_email.gemspec
-gemspec
-
 gem 'rails'
 
-group :development, :test do
-  gem 'rspec', '~> 3'
-  gem 'sqlite3'
-  gem 'capybara'
-  gem 'coveralls', require: false
-end
+# Specify your gem's dependencies in devise-multi_email.gemspec
+gemspec
 

data/README.md

@@ -1,22 +1,22 @@
 # Devise::MultiEmail [![Build Status](https://travis-ci.org/allenwq/devise-multi_email.svg?branch=master)](https://travis-ci.org/allenwq/devise-multi_email) [![Coverage Status](https://coveralls.io/repos/allenwq/devise-multi_email/badge.svg?branch=master&service=github)](https://coveralls.io/github/allenwq/devise-multi_email?branch=master)
 
-Let [devise](https://github.com/plataformatec/devise) support multilpe emails, it allows you to:
+Letting [Devise](https://github.com/plataformatec/devise) support multiple emails, allows you to:
 - Login with multiple emails
 - Send confirmations to multiple emails
 - Recover the password with any of the emails
-- Validations for multiple emails 
+- Validations for multiple emails
 
-`:multi_email_authenticatable`, `:multi_email_confirmable` and `:multi_email_validatable` are provided by devise-multi_email.
+`:multi_email_authenticatable`, `:multi_email_confirmable` and `:multi_email_validatable` are provided by _devise-multi_email_.
 
 ## Getting Started
 
-Add this line to your application's Gemfile, devise-multi_email has been tested with devise 4.0 and rails 4.2:
+Add this line to your application's `Gemfile`, _devise-multi_email_ has been tested with Devise 4.0 and rails 4.2:
 
 ```ruby
 gem 'devise-multi_email'
 ```
 
-Suppose you have already setup devise, your `User` model might look like this:
+Suppose you have already setup Devise, your `User` model might look like this:
 
 ```ruby
 class User < ActiveRecord::Base
@@ -24,7 +24,7 @@ class User < ActiveRecord::Base
 end
 ```
 
-In order to let your `User` support multiple emails, with `devise-multi_email` what you need to do is just:
+In order to let your `User` support multiple emails, with _devise-multi_email_ what you need to do is just:
 
 ```ruby
 class User < ActiveRecord::Base
@@ -39,7 +39,8 @@ class Email < ActiveRecord::Base
 end
 ```
 
-Note that `:email` column should be moved from users table to the emails table, and a new `primary` boolean column should be added to the emails table (so that all the emails will be sent to the primary email, and `user.email` will give you the primary email address). Your emails table's migration should look like:
+Note that the `:email` column should be moved from `users` table to the `emails` table, and a new `primary` boolean column should be added to the `emails` table (so that all the emails will be sent to the primary email, and `user.email` will give you the primary email address). Your `emails` table's migration should look like:
+
 ```ruby
 create_table :emails do |t|
   t.integer :user_id
@@ -48,20 +49,48 @@ create_table :emails do |t|
  end
 ```
 
+### Configure custom association names
+
+You may not want to use the association `user.emails` or `email.users`. You can customize the name of the associations used. Add your custom configurations to an initializer file such as `config/initializers/devise-multi_email.rb`.
+
+_Note: model classes are inferred from the associations._
+
+```ruby
+Devise::MultiEmail.configure do |config|
+  # Default is :user for Email model
+  config.parent_association_name = :team
+  # Default is :emails for parent (e.g. User) model
+  config.emails_association_name = :email_addresses
+  # For backwards-compatibility, specify :primary_email_record
+  # Default is :primary_email
+  config.primary_email_method_name = :primary_email_record
+end
+
+# Example use of custom association names
+team = Team.first
+emails = team.email_addresses
+
+email = EmailAddress.first
+team = email.team
+```
+
 ## Confirmable with multiple emails
-Sending different confirmaitons to different emails is supported. What you need to do is:
+
+Sending separate confirmations to each email is supported. What you need to do is:
 
 Declare `devise :multi_email_confirmable` in your `User` model:
+
 ```ruby
 class User < ActiveRecord::Base
   has_many :emails
 
-  # You should not declare :confiramble and :multi_email_confirmable at the same time.
+  # You should not declare :confirmable and :multi_email_confirmable at the same time.
   devise :multi_email_authenticatable, :registerable, :multi_email_confirmable
 end
 ```
 
-Add `:confirmation_token`, `:confirmed_at` and `:confirmation_sent_at` to your emails table:
+Add `:confirmation_token`, `:confirmed_at` and `:confirmation_sent_at` to your `emails` table:
+
 ```ruby
 create_table :emails do |t|
   t.integer :user_id
@@ -69,16 +98,18 @@ create_table :emails do |t|
   t.boolean :primary, default: false
 
   ## Confirmable
-  t.string   :confirmation_token
+  t.string :unconfirmed_email
+  t.string :confirmation_token
   t.datetime :confirmed_at
   t.datetime :confirmation_sent_at
 end
 ```
 
-Then all the methods in devise confirmable are avalible in your `Email` model. You can do `Email#send_confirmation_instructions` for each of your email. And `User#send_confirmation_instructions` will be delegated to the primary email.
+Then all the methods in Devise confirmable are available in your `Email` model. You can do `email#send_confirmation_instructions` for each of your email. And `user#send_confirmation_instructions` will be delegated to the primary email.
 
 ## Validatable with multiple emails
-Declare `devise :multi_email_validatable` in the user model, then all the user emails will be validated:
+
+Declare `devise :multi_email_validatable` in the `User` model, then all the user emails will be validated:
 
 ```ruby
 class User < ActiveRecord::Base
@@ -89,18 +120,39 @@ class User < ActiveRecord::Base
 end
 ```
 
+You can find the detailed configurations in the [rails 5 example app](https://github.com/allenwq/devise-multi_email/tree/master/examples/rails5_app).
+
+## ActiveJob Integration
+
+The [Devise README](https://github.com/plataformatec/devise#activejob-integration) describes how to use ActiveJob to deliver emails in the background. Normally you would place the following code in your `User` model, however when using _devise-multi_email_ you should place this in the `Email` model.
+
+```ruby
+# models/email.rb
+def send_devise_notification(notification, *args)
+  devise_mailer.send(notification, self, *args).deliver_later
+end
+```
+
 ## What's more
 
-The gem works with all other devise modules just as normal, you don't need to add the `multi_email` prefix.
+The gem works with all other Devise modules as expected -- you don't need to add the "multi_email" prefix.
+
 ```ruby
-  devise :multi_email_authenticatable, :multi_email_confirmable, :multi_email_validatable, :lockable, 
+class User < ActiveRecord::Base
+  devise :multi_email_authenticatable, :multi_email_confirmable, :multi_email_validatable, :lockable,
          :recoverable, :registerable, :rememberable, :timeoutable, :trackable
+end
 ```
 
 ## Issues
-You need to implement add/delete emails for a user as well as set/unset primary email.
 
-You can do `email.send_confirmation_instructions` for every email, but you also need to handle this logic in some place(excpet for the primary email). e.g. After a new email was added by a user, you might want to provide some buttons to allow user to resend confirmation instrucitons for that email.
+You need to implement add/delete emails for a user as well as set/unset "primary" for each email.
+
+You can do `email.send_confirmation_instructions` for each email individually, but you need to handle that logic in some place (except for the primary email, which is handled by Devise by default). e.g. After a new email was added by a user, you might want to provide some buttons in the view to allow users to resend confirmation instructions for that email.
+
+## Wiki
+
+[Migrating exiting user records](https://github.com/allenwq/devise-multi_email/wiki/Migrating-existing-user-records)
 
 ## Development
 
@@ -116,4 +168,3 @@ Bug reports and pull requests are welcome on GitHub at https://github.com/[USERN
 ## License
 
 The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).
-

data/devise-multi_email.gemspec

@@ -23,4 +23,8 @@ Gem::Specification.new do |spec|
 
   spec.add_development_dependency 'bundler', '~> 1.10'
   spec.add_development_dependency 'rake', '~> 10.0'
+  spec.add_development_dependency 'rspec'
+  spec.add_development_dependency 'sqlite3'
+  spec.add_development_dependency 'capybara'
+  spec.add_development_dependency 'coveralls'
 end

data/examples/rails5_app/.gitignore

@@ -0,0 +1,21 @@
+# See https://help.github.com/articles/ignoring-files for more about ignoring files.
+#
+# If you find yourself ignoring temporary files generated by your text editor
+# or operating system, you probably want to add a global ignore instead:
+#   git config --global core.excludesfile '~/.gitignore_global'
+
+# Ignore bundler config.
+/.bundle
+
+# Ignore the default SQLite database.
+/db/*.sqlite3
+/db/*.sqlite3-journal
+
+# Ignore all logfiles and tempfiles.
+/log/*
+/tmp/*
+!/log/.keep
+!/tmp/.keep
+
+# Ignore Byebug command history file.
+.byebug_history

data/examples/rails5_app/Gemfile

@@ -0,0 +1,55 @@
+source 'https://rubygems.org'
+
+git_source(:github) do |repo_name|
+  repo_name = "#{repo_name}/#{repo_name}" unless repo_name.include?("/")
+  "https://github.com/#{repo_name}.git"
+end
+
+
+# Bundle edge Rails instead: gem 'rails', github: 'rails/rails'
+gem 'rails', '~> 5.0.2'
+# Use sqlite3 as the database for Active Record
+gem 'sqlite3'
+# Use Puma as the app server
+gem 'puma', '~> 3.0'
+# Use SCSS for stylesheets
+gem 'sass-rails', '~> 5.0'
+# Use Uglifier as compressor for JavaScript assets
+gem 'uglifier', '>= 1.3.0'
+# See https://github.com/rails/execjs#readme for more supported runtimes
+# gem 'therubyracer', platforms: :ruby
+
+# Use jquery as the JavaScript library
+gem 'jquery-rails'
+# Turbolinks makes navigating your web application faster. Read more: https://github.com/turbolinks/turbolinks
+gem 'turbolinks', '~> 5'
+# Build JSON APIs with ease. Read more: https://github.com/rails/jbuilder
+gem 'jbuilder', '~> 2.5'
+# Use Redis adapter to run Action Cable in production
+# gem 'redis', '~> 3.0'
+# Use ActiveModel has_secure_password
+# gem 'bcrypt', '~> 3.1.7'
+
+# Use Capistrano for deployment
+# gem 'capistrano-rails', group: :development
+
+group :development, :test do
+  # Call 'byebug' anywhere in the code to stop execution and get a debugger console
+  gem 'byebug', platform: :mri
+end
+
+group :development do
+  # Access an IRB console on exception pages or by using <%= console %> anywhere in the code.
+  gem 'web-console', '>= 3.3.0'
+  gem 'listen', '~> 3.0.5'
+  # Spring speeds up development by keeping your application running in the background. Read more: https://github.com/rails/spring
+  gem 'spring'
+  gem 'spring-watcher-listen', '~> 2.0.0'
+end
+
+# Windows does not include zoneinfo files, so bundle the tzinfo-data gem
+gem 'tzinfo-data', platforms: [:mingw, :mswin, :x64_mingw, :jruby]
+
+gem 'devise'
+gem 'devise-multi_email'
+gem 'devise-encryptable'

data/examples/rails5_app/Gemfile.lock

@@ -0,0 +1,185 @@
+GEM
+  remote: https://rubygems.org/
+  specs:
+    actioncable (5.0.2)
+      actionpack (= 5.0.2)
+      nio4r (>= 1.2, < 3.0)
+      websocket-driver (~> 0.6.1)
+    actionmailer (5.0.2)
+      actionpack (= 5.0.2)
+      actionview (= 5.0.2)
+      activejob (= 5.0.2)
+      mail (~> 2.5, >= 2.5.4)
+      rails-dom-testing (~> 2.0)
+    actionpack (5.0.2)
+      actionview (= 5.0.2)
+      activesupport (= 5.0.2)
+      rack (~> 2.0)
+      rack-test (~> 0.6.3)
+      rails-dom-testing (~> 2.0)
+      rails-html-sanitizer (~> 1.0, >= 1.0.2)
+    actionview (5.0.2)
+      activesupport (= 5.0.2)
+      builder (~> 3.1)
+      erubis (~> 2.7.0)
+      rails-dom-testing (~> 2.0)
+      rails-html-sanitizer (~> 1.0, >= 1.0.3)
+    activejob (5.0.2)
+      activesupport (= 5.0.2)
+      globalid (>= 0.3.6)
+    activemodel (5.0.2)
+      activesupport (= 5.0.2)
+    activerecord (5.0.2)
+      activemodel (= 5.0.2)
+      activesupport (= 5.0.2)
+      arel (~> 7.0)
+    activesupport (5.0.2)
+      concurrent-ruby (~> 1.0, >= 1.0.2)
+      i18n (~> 0.7)
+      minitest (~> 5.1)
+      tzinfo (~> 1.1)
+    arel (7.1.4)
+    bcrypt (3.1.11)
+    builder (3.2.3)
+    byebug (9.0.6)
+    concurrent-ruby (1.0.5)
+    debug_inspector (0.0.2)
+    devise (4.2.0)
+      bcrypt (~> 3.0)
+      orm_adapter (~> 0.1)
+      railties (>= 4.1.0, < 5.1)
+      responders
+      warden (~> 1.2.3)
+    devise-encryptable (0.2.0)
+      devise (>= 2.1.0)
+    devise-multi_email (1.0.5)
+      devise
+    erubis (2.7.0)
+    execjs (2.7.0)
+    ffi (1.9.18)
+    globalid (0.3.7)
+      activesupport (>= 4.1.0)
+    i18n (0.8.1)
+    jbuilder (2.6.3)
+      activesupport (>= 3.0.0, < 5.2)
+      multi_json (~> 1.2)
+    jquery-rails (4.2.2)
+      rails-dom-testing (>= 1, < 3)
+      railties (>= 4.2.0)
+      thor (>= 0.14, < 2.0)
+    listen (3.0.8)
+      rb-fsevent (~> 0.9, >= 0.9.4)
+      rb-inotify (~> 0.9, >= 0.9.7)
+    loofah (2.0.3)
+      nokogiri (>= 1.5.9)
+    mail (2.6.4)
+      mime-types (>= 1.16, < 4)
+    method_source (0.8.2)
+    mime-types (3.1)
+      mime-types-data (~> 3.2015)
+    mime-types-data (3.2016.0521)
+    mini_portile2 (2.1.0)
+    minitest (5.10.1)
+    multi_json (1.12.1)
+    nio4r (2.0.0)
+    nokogiri (1.7.0.1)
+      mini_portile2 (~> 2.1.0)
+    orm_adapter (0.5.0)
+    puma (3.7.1)
+    rack (2.0.1)
+    rack-test (0.6.3)
+      rack (>= 1.0)
+    rails (5.0.2)
+      actioncable (= 5.0.2)
+      actionmailer (= 5.0.2)
+      actionpack (= 5.0.2)
+      actionview (= 5.0.2)
+      activejob (= 5.0.2)
+      activemodel (= 5.0.2)
+      activerecord (= 5.0.2)
+      activesupport (= 5.0.2)
+      bundler (>= 1.3.0, < 2.0)
+      railties (= 5.0.2)
+      sprockets-rails (>= 2.0.0)
+    rails-dom-testing (2.0.2)
+      activesupport (>= 4.2.0, < 6.0)
+      nokogiri (~> 1.6)
+    rails-html-sanitizer (1.0.3)
+      loofah (~> 2.0)
+    railties (5.0.2)
+      actionpack (= 5.0.2)
+      activesupport (= 5.0.2)
+      method_source
+      rake (>= 0.8.7)
+      thor (>= 0.18.1, < 2.0)
+    rake (12.0.0)
+    rb-fsevent (0.9.8)
+    rb-inotify (0.9.8)
+      ffi (>= 0.5.0)
+    responders (2.3.0)
+      railties (>= 4.2.0, < 5.1)
+    sass (3.4.23)
+    sass-rails (5.0.6)
+      railties (>= 4.0.0, < 6)
+      sass (~> 3.1)
+      sprockets (>= 2.8, < 4.0)
+      sprockets-rails (>= 2.0, < 4.0)
+      tilt (>= 1.1, < 3)
+    spring (2.0.1)
+      activesupport (>= 4.2)
+    spring-watcher-listen (2.0.1)
+      listen (>= 2.7, < 4.0)
+      spring (>= 1.2, < 3.0)
+    sprockets (3.7.1)
+      concurrent-ruby (~> 1.0)
+      rack (> 1, < 3)
+    sprockets-rails (3.2.0)
+      actionpack (>= 4.0)
+      activesupport (>= 4.0)
+      sprockets (>= 3.0.0)
+    sqlite3 (1.3.13)
+    thor (0.19.4)
+    thread_safe (0.3.6)
+    tilt (2.0.6)
+    turbolinks (5.0.1)
+      turbolinks-source (~> 5)
+    turbolinks-source (5.0.0)
+    tzinfo (1.2.2)
+      thread_safe (~> 0.1)
+    uglifier (3.1.4)
+      execjs (>= 0.3.0, < 3)
+    warden (1.2.7)
+      rack (>= 1.0)
+    web-console (3.4.0)
+      actionview (>= 5.0)
+      activemodel (>= 5.0)
+      debug_inspector
+      railties (>= 5.0)
+    websocket-driver (0.6.5)
+      websocket-extensions (>= 0.1.0)
+    websocket-extensions (0.1.2)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  byebug
+  devise
+  devise-encryptable
+  devise-multi_email
+  jbuilder (~> 2.5)
+  jquery-rails
+  listen (~> 3.0.5)
+  puma (~> 3.0)
+  rails (~> 5.0.2)
+  sass-rails (~> 5.0)
+  spring
+  spring-watcher-listen (~> 2.0.0)
+  sqlite3
+  turbolinks (~> 5)
+  tzinfo-data
+  uglifier (>= 1.3.0)
+  web-console (>= 3.3.0)
+
+BUNDLED WITH
+   1.13.6

data/examples/rails5_app/README.md

@@ -0,0 +1,24 @@
+# README
+
+This README would normally document whatever steps are necessary to get the
+application up and running.
+
+Things you may want to cover:
+
+* Ruby version
+
+* System dependencies
+
+* Configuration
+
+* Database creation
+
+* Database initialization
+
+* How to run the test suite
+
+* Services (job queues, cache servers, search engines, etc.)
+
+* Deployment instructions
+
+* ...

data/examples/rails5_app/Rakefile

@@ -0,0 +1,6 @@
+# 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_relative 'config/application'
+
+Rails.application.load_tasks

data/examples/rails5_app/app/assets/config/manifest.js

@@ -0,0 +1,3 @@
+//= link_tree ../images
+//= link_directory ../javascripts .js
+//= link_directory ../stylesheets .css

data/examples/rails5_app/app/assets/javascripts/application.js

@@ -0,0 +1,16 @@
+// 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 any plugin's vendor/assets/javascripts directory 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
+// compiled file. JavaScript code in this file should be added after the last require_* statement.
+//
+// Read Sprockets README (https://github.com/rails/sprockets#sprockets-directives) for details
+// about supported directives.
+//
+//= require jquery
+//= require jquery_ujs
+//= require turbolinks
+//= require_tree .

data/examples/rails5_app/app/assets/javascripts/cable.js

@@ -0,0 +1,13 @@
+// Action Cable provides the framework to deal with WebSockets in Rails.
+// You can generate new channels where WebSocket features live using the rails generate channel command.
+//
+//= require action_cable
+//= require_self
+//= require_tree ./channels
+
+(function() {
+  this.App || (this.App = {});
+
+  App.cable = ActionCable.createConsumer();
+
+}).call(this);

data/examples/rails5_app/app/assets/stylesheets/application.css

@@ -0,0 +1,15 @@
+/*
+ * 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 any plugin's vendor/assets/stylesheets directory 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 bottom of the
+ * compiled file so the styles you add here take precedence over styles defined in any other CSS/SCSS
+ * files in this directory. Styles in this file should be added after the last require_* statement.
+ * It is generally better to create a new file per style scope.
+ *
+ *= require_tree .
+ *= require_self
+ */

data/examples/rails5_app/app/channels/application_cable/channel.rb

@@ -0,0 +1,4 @@
+module ApplicationCable
+  class Channel < ActionCable::Channel::Base
+  end
+end

data/examples/rails5_app/app/channels/application_cable/connection.rb

@@ -0,0 +1,4 @@
+module ApplicationCable
+  class Connection < ActionCable::Connection::Base
+  end
+end

data/examples/rails5_app/app/controllers/application_controller.rb

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

data/examples/rails5_app/app/helpers/application_helper.rb

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

data/examples/rails5_app/app/jobs/application_job.rb

@@ -0,0 +1,2 @@
+class ApplicationJob < ActiveJob::Base
+end

data/examples/rails5_app/app/mailers/application_mailer.rb

@@ -0,0 +1,4 @@
+class ApplicationMailer < ActionMailer::Base
+  default from: 'from@example.com'
+  layout 'mailer'
+end

data/examples/rails5_app/app/models/application_record.rb

@@ -0,0 +1,3 @@
+class ApplicationRecord < ActiveRecord::Base
+  self.abstract_class = true
+end

data/examples/rails5_app/app/models/email.rb

@@ -0,0 +1,3 @@
+class Email < ApplicationRecord
+  belongs_to :user
+end

data/examples/rails5_app/app/models/user.rb

@@ -0,0 +1,9 @@
+class User < ApplicationRecord
+  has_many :emails
+  # Include default devise modules. Others available are:
+  # :lockable, :timeoutable and :omniauthable
+  devise :multi_email_authenticatable, :multi_email_confirmable, :multi_email_validatable,
+         :recoverable, :registerable, :rememberable, :trackable,
+         # Below are for testing purpose, not required by default
+         :encryptable, encryptor: :sha512
+end