amandragon/contacts

A rails app to demonstrate the concepts of problems with fat controllers.

Rails fat controllers

This app demonstrates the pitfalls of implementing fat controllers.

Goal

• Move code that belongs in models out of the controller.

How you'll get there

• You'll get the model spec examples to pass
• Use ActiveRecord methods and SQL statements to accomplish this.
• You'll also need to create a couple of migrations!

Before you start

After you've forked and cloned this repo

• Run rake db:migrate && rake db:test:prepare at the terminal
• Run rake db:seed at the terminal to populate the db with seed data
  • Take a look at the file db/seeds.rb to see how this actually works

##Get the specs to pass for

Person.all_email_domains

• Note/hint: You'll want to do this first

• Note/hint: You'll need to create a migration that will add the domain_name:string field to the people table

• Also, you'll want to create a separate migration to extract domain names from people email fields and move them into people domain_name fields, which you had created with the previous migration. Note: You'll need to look up how to save ActiveRecord objects while iterating through them and moving data around

• To get a quick refresher on how to generate a migration, check this out: http://guides.rubyonrails.org/migrations.html#creating-a-standalone-migration

• You'll want to select distinct domain names :) Look up how to do it here: http://guides.rubyonrails.org/active_record_querying.html#selecting-specific-fields

Person.find_all_with_email_domain

Resources used

Thanks http://www.briandunning.com/sample-data/ for the sample data!