clean up removed bower components

Author: ljones140

app/controllers/questions_controller.rb

@@ -1,5 +1,5 @@
 class QuestionsController < ApplicationController
-
+  
   before_action :check_if_question_owner, only: [:show, :destroy, :edit, :update]
   before_action :check_if_event_owner, only: [:new]
 
@@ -96,5 +96,5 @@ def question_number(event, question)
   def question_params
     params.require(:question).permit(:content, choices_attributes:[:content])
   end
-  
+
 end

spec/factories/questions.rb

@@ -1,5 +1,4 @@
 FactoryGirl.define do
-
   factory :question do
     content "My Question"
   end

spec/models/choice_spec.rb

@@ -1,9 +1,9 @@
 require 'rails_helper'
 
 RSpec.describe Choice, type: :model do
+  
   let(:event){ create :event, user: (create :user) }
 
-
   it { is_expected.to belong_to :question }
   it { is_expected.to have_many :votes }
   it { is_expected.to validate_presence_of :content }
@@ -16,4 +16,4 @@
     expect{ question.destroy }.to change{Choice.count}.by -1
     expect(question.choices.include? choice).to eq false
   end
-end
+end

spec/models/event_spec.rb

@@ -1,19 +1,17 @@
 require 'rails_helper'
 
 RSpec.describe Event, type: :model do
-  let(:user){ create :user }
 
+  let(:user){ create :user }
 
   it { is_expected.to validate_presence_of :user }
   it { is_expected.to validate_presence_of :title }
   it { is_expected.to belong_to :user }
   it { is_expected.to have_many :questions }
   it { is_expected.to have_many :voters }
 
-
   it 'is destroyed when parent user is destroyed' do
     event = create :event, user: user
-
     expect{ user.destroy }.to change{ Event.count }.by -1
     expect( user.events.include? event ).to eq false
   end
@@ -24,4 +22,4 @@
       expect{ Event.create(title: 'test', user: user) }.to change{ Event.count }.by(1)
     end
   end
-end
+end

spec/models/question_spec.rb

@@ -1,12 +1,11 @@
 require 'rails_helper'
 
 RSpec.describe Question, type: :model do
-  let(:user){ create :user }
 
+  let(:user){ create :user }
 
   it { is_expected.to belong_to :event }
   it { is_expected.to have_many :choices }
-  
   it { is_expected.to validate_presence_of :event }
   it { is_expected.to validate_presence_of :content }
 
@@ -17,4 +16,4 @@
     expect{ event.destroy }.to change{ Question.count }.by -1
     expect( event.questions.include? question ).to eq false
   end
-end
+end

spec/models/vote_spec.rb

@@ -1,22 +1,21 @@
 require 'rails_helper'
 
 RSpec.describe Vote, type: :model do
+
   let(:event){ create :event, user: (create :user) }
   let(:question){ create :question, event: event }
   let(:choice){ create :choice, question: question }
 
-
   it { is_expected.to belong_to :choice }
   it { is_expected.to belong_to :voter }
   it { is_expected.to validate_presence_of :choice }
 
   it "can be created on a choice" do
-    expect{choice.votes.create}.to change{choice.votes.count}.by 1
+    expect{ choice.votes.create }.to change{ choice.votes.count }.by 1
   end
 
   it 'is destroyed when parent choice is destroyed' do
     vote = create :vote, choice: choice
-
     expect{ choice.destroy }.to change{ Vote.count }.by -1
     expect( choice.votes.include? vote ).to eq false
   end

spec/spec_helper.rb

@@ -1,95 +1,13 @@
 require 'coveralls'
 Coveralls.wear!('rails')
 
-# This file was generated by the `rails generate rspec:install` command. Conventionally, all
-# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
-# The generated `.rspec` file contains `--require spec_helper` which will cause
-# this file to always be loaded, without a need to explicitly require it in any
-# files.
-#
-# Given that it is always loaded, you are encouraged to keep this file as
-# light-weight as possible. Requiring heavyweight dependencies from this file
-# will add to the boot time of your test suite on EVERY test run, even for an
-# individual file that may not need all of that loaded. Instead, consider making
-# a separate helper file that requires the additional dependencies and performs
-# the additional setup, and require it from the spec files that actually need
-# it.
-#
-# The `.rspec` file also contains a few flags that are not defaults but that
-# users commonly want.
-#
-# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
 RSpec.configure do |config|
-  # rspec-expectations config goes here. You can use an alternate
-  # assertion/expectation library such as wrong or the stdlib/minitest
-  # assertions if you prefer.
+
   config.expect_with :rspec do |expectations|
-    # This option will default to `true` in RSpec 4. It makes the `description`
-    # and `failure_message` of custom matchers include text for helper methods
-    # defined using `chain`, e.g.:
-    #     be_bigger_than(2).and_smaller_than(4).description
-    #     # => "be bigger than 2 and smaller than 4"
-    # ...rather than:
-    #     # => "be bigger than 2"
     expectations.include_chain_clauses_in_custom_matcher_descriptions = true
   end
 
-  # rspec-mocks config goes here. You can use an alternate test double
-  # library (such as bogus or mocha) by changing the `mock_with` option here.
   config.mock_with :rspec do |mocks|
-    # Prevents you from mocking or stubbing a method that does not exist on
-    # a real object. This is generally recommended, and will default to
-    # `true` in RSpec 4.
     mocks.verify_partial_doubles = true
   end
-
-# The settings below are suggested to provide a good initial experience
-# with RSpec, but feel free to customize to your heart's content.
-=begin
-  # These two settings work together to allow you to limit a spec run
-  # to individual examples or groups you care about by tagging them with
-  # `:focus` metadata. When nothing is tagged with `:focus`, all examples
-  # get run.
-  config.filter_run :focus
-  config.run_all_when_everything_filtered = true
-
-  # Allows RSpec to persist some state between runs in order to support
-  # the `--only-failures` and `--next-failure` CLI options. We recommend
-  # you configure your source control system to ignore this file.
-  config.example_status_persistence_file_path = "spec/examples.txt"
-
-  # Limits the available syntax to the non-monkey patched syntax that is
-  # recommended. For more details, see:
-  #   - http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax
-  #   - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
-  #   - http://myronmars.to/n/dev-blog/2014/05/notable-changes-in-rspec-3#new__config_option_to_disable_rspeccore_monkey_patching
-  config.disable_monkey_patching!
-
-  # Many RSpec users commonly either run the entire suite or an individual
-  # file, and it's useful to allow more verbose output when running an
-  # individual spec file.
-  if config.files_to_run.one?
-    # Use the documentation formatter for detailed output,
-    # unless a formatter has already been configured
-    # (e.g. via a command-line flag).
-    config.default_formatter = 'doc'
-  end
-
-  # Print the 10 slowest examples and example groups at the
-  # end of the spec run, to help surface which specs are running
-  # particularly slow.
-  config.profile_examples = 10
-
-  # Run specs in random order to surface order dependencies. If you find an
-  # order dependency and want to debug it, you can fix the order by providing
-  # the seed, which is printed after each run.
-  #     --seed 1234
-  config.order = :random
-
-  # Seed global randomization in this process using the `--seed` CLI option.
-  # Setting this allows you to use `--seed` to deterministically reproduce
-  # test failures related to randomization by passing the same `--seed` value
-  # as the one that triggered the failure.
-  Kernel.srand config.seed
-=end
 end

spec/support/helpers/connect.rb

@@ -1,6 +1,5 @@
 module ConnectHelpers
   def connect
-    # page.driver.block_unknown_urls
     visit "/"
 
     Timeout.timeout(5) do

spec/support/helpers/data_creator.rb

@@ -38,7 +38,6 @@ def vote_creator(choice_id, count)
 
 end
 
-
 RSpec.configure do |config|
   config.include(DataHelpers)
 end