cacheable_flash 0.2.10 → 0.3.0

data/CHANGELOG

@@ -1,3 +1,14 @@
+0.3.0 - AUG.21.2012
+- Completed integration with stackable_flash (http://github.com/pboling/stackable_flash)
+- Test::Unit helpers and Rspec Matchers updated to be stackable
+- Expanded test suite
+- Cleaned up both Middleware and Around Filter integration points
+- Rspec Matchers now have pretty failure messages
+- Removed dependency on facets gem
+- Allows any data type to be stored in the cookie.  Only escapes strings.
+  - Does not convert flash value to string before storing in cookie if value is a number
+  - (v0.2.X converted everything to string)
+
 0.2.10 - AUG.13.2012
 - Split test_helpers from rspec_matchers (test_helpers may be useful in TestUnit
 - When using Middleware: Flash Cookies now stay in the cookie until cleared out by the javascript: closer to guaranteed delivery.

data/README.rdoc

@@ -10,14 +10,8 @@ your application.
 
 == Installation as gem
 
-gem install 'cacheable_flash'
-
-add to your Gemfile:
-gem 'cacheable_flash'
-
-== Installation as plugin (For old Rails)
-
-ruby script/plugin install git://github.com/pivotal/cacheable-flash.git
+  gem 'cacheable_flash' # added to your Gemfile
+  $ bundle install
 
 == Setup
 
@@ -149,13 +143,12 @@ Cacheable Flash provides test helpers which includes the flash_cookie method.
 
 == Contributing to cacheable-flash
 
-* Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet
-* Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it
-* Fork the project
-* Start a feature/bugfix branch
-* Commit and push until you are happy with your contribution
-* Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
-* Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Added some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
+6. Create new Pull Request
 
 == Copyright
 
@@ -163,6 +156,3 @@ Licensed under the MIT License.
 
 - Copyright (c) 2011-2012 Peter H. Boling (http://peterboling.com). See LICENSE for further details.
 - Copyright (c) 2007-2010 Pivotal Labs
-
-
-

data/cacheable_flash.gemspec

@@ -23,15 +23,13 @@ Gem::Specification.new do |s|
   s.rubygems_version = "1.8.24"
   s.summary = "Render flash messages from a cookie using JavaScript, instead of in your Rails view template"
 
-  s.add_runtime_dependency(%q<facets>, [">= 0"])
+  s.add_runtime_dependency(%q<stackable_flash>, [">= 0.0.4"])
   s.add_runtime_dependency(%q<json>, [">= 0"])
   s.add_development_dependency(%q<rails>, ["~> 3.1.3"])
   s.add_development_dependency(%q<jquery-rails>, [">= 0"])
-  s.add_development_dependency(%q<rspec-rails>, [">= 2.8.0"])
+  s.add_development_dependency(%q<rspec-rails>, [">= 2.11.0"])
   s.add_development_dependency(%q<rdoc>, [">= 3.12"])
-  s.add_development_dependency(%q<bundler>, [">= 1.0.24"])
-  s.add_development_dependency(%q<jeweler>, [">= 1.6.4"])
   s.add_development_dependency(%q<reek>, [">= 1.2.8"])
   s.add_development_dependency(%q<roodi>, [">= 2.1.0"])
+  s.add_development_dependency(%q<rake>, [">= 0"])
 end
-

data/lib/cacheable_flash.rb

@@ -1,11 +1,12 @@
 require 'json'
+require 'stackable_flash'
 
 module CacheableFlash
   if defined?(Rails) && ::Rails::VERSION::MAJOR == 3
     require 'cacheable_flash/middleware'
     require 'cacheable_flash/engine' if ::Rails::VERSION::MINOR >= 1
     require 'cacheable_flash/railtie'
-  else 
+  else
     # For older rails use generator
   end
 

data/lib/cacheable_flash/config.rb

@@ -1,19 +1,31 @@
-require 'facets/module/mattr' # gives cattr
-
 module CacheableFlash
   class Config
 
+    class << self
+      attr_accessor :config
+    end
+
     DEFAULTS = {
       # Specify how multiple flashes at the same key (e.g. :notice, :errors) should be handled
-      :append_as => :br, # or :array
+      :append_as => :br, # or :array, :p, :ul, :ol, or a proc or lambda of your own design
     }
 
-    cattr_reader :config
-    cattr_writer :config
-
     self.config ||= DEFAULTS
     def self.configure &block
       yield @@config
+      StackableFlash::Config.configure do
+        if self.config[:append_as].respond_to?(:call)
+          config[:stack_with_proc] = self.config[:append_as]
+        else
+          config[:stack_with_proc] = case self.config[:append_as]
+            when :br then Proc.new {|arr| arr.join('<br/>') }
+            when :array then Proc.new {|arr| arr }
+            when :p then Proc.new {|arr| arr.map! {|x| "<p>#{x}</p>"}.join }
+            when :ul then Proc.new {|arr| '<ul>' + arr.map! {|x| "<li>#{x}</li>"}.join + '</ul>' }
+            when :ol then Proc.new {|arr| '<ol>' + arr.map! {|x| "<li>#{x}</li>"}.join + '</ol>' }
+          end
+        end
+      end
     end
 
     def self.[](key)

data/lib/cacheable_flash/cookie_flash.rb

@@ -1,32 +1,27 @@
 module CacheableFlash
   module CookieFlash
     def cookie_flash(flash, cookies)
-      cookie_flash = (JSON(cookies['flash']) if cookies['flash']) || {} rescue {}
-
+      cflash = (JSON.parse(cookies['flash']) if cookies['flash']) || {} rescue {}
       flash.each do |key, value|
-        value = ERB::Util.html_escape(value) unless value.is_a?(Hash) || value.html_safe?
-        if cookie_flash[key.to_s].blank?
-          value_as_string = value.kind_of?(Numeric) ? value.to_s : value
-          case CacheableFlash::Config[:append_as]
-            when :br then
-              cookie_flash[key.to_s] = value_as_string
-            when :array then
-              cookie_flash[key.to_s] = Array(value_as_string)
-            else
-              raise "CacheableFlash: #{CacheableFlash::Config.config[:append_as]} is not a valid value for CacheableFlash::Config.config[:append_as]"
+        # Since v0.3.0 only escaping strings
+        if value.kind_of?(String)
+          value = ERB::Util.html_escape(value) unless value.html_safe?
+        end
+        # This allows any data type to be stored in the cookie; important for using an array as the value with
+        # stackable_flash
+        skey = key.to_s
+        if cflash[skey].kind_of?(Array) # Stackable!!!
+          if value.kind_of?(Array)
+            cflash[skey] += value # Add the values from the other array, which is already a stackable flash
+          else
+            cflash[skey] << value
           end
         else
-          case CacheableFlash::Config[:append_as]
-            when :br then
-              cookie_flash[key.to_s] << "<br/>#{value}"
-            when :array then
-              cookie_flash[key.to_s] << "#{value}"
-            else
-              raise "CacheableFlash: #{CacheableFlash::Config.config[:append_as]} is not a valid value for CacheableFlash::Config.config[:append_as]"
-          end
+          cflash[skey] = value
         end
       end
-      cookie_flash.to_json.gsub("+", "%2B")
+      # I have forgotten why the gsub + matters, so NOTE: to future self: document weird shit.
+      cflash.to_json.gsub("+", "%2B")
     end
   end
 end

data/lib/cacheable_flash/middleware.rb

@@ -12,26 +12,27 @@ module CacheableFlash
     #   to ensure they are seen and not lost, so we grab them from the rails flash hash, or the request cookies
     def call(env)
       status, headers, body = @app.call(env)
-      flash = env[FLASH_HASH_KEY]
+      env_flash = env[FLASH_HASH_KEY]
 
-      if flash
+      if env_flash
         response = Rack::Response.new(body, status, headers)
         cookies = env["rack.cookies"] || {}
-        response.set_cookie("flash", { :value => cookie_flash(flash, cookies), :path => "/" })
+        response.set_cookie("flash", { :value => cookie_flash(env_flash, cookies), :path => "/" })
         response.finish
       else
         request = ActionDispatch::Request.new(env)
-        cookie_flash = request.respond_to?(:cookie_jar) ?
+        cflash = request.respond_to?(:cookie_jar) ?
           request.cookie_jar['flash'] :
           nil
-        if cookie_flash
+        if cflash
           response = Rack::Response.new(body, status, headers)
-          response.set_cookie("flash", { :value => cookie_flash, :path => "/" })
+          response.set_cookie("flash", { :value => cflash, :path => "/" })
           response.finish
         else
-          [status, headers, body]
+          response = body
         end
       end
+      [status, headers, response]
     end
 
   end

data/lib/cacheable_flash/rspec_matchers.rb

@@ -3,20 +3,31 @@ require 'cacheable_flash/test_helpers'
 module CacheableFlash
   module RspecMatchers
     include CacheableFlash::TestHelpers
-    RSpec::Matchers.define :have_flash_cookie do |flash_status, regex|
+    RSpec::Matchers.define :have_flash_cookie do |flash_status, expecting|
       define_method :has_flash_cookie? do |response|
-        regex = /#{Regexp.escape(regex)}/ if regex.is_a?(String)
-
-        cook = begin
-          response.cookies['flash'] ?
-            JSON(response.cookies['flash']) :
-            {}
-        rescue JSON::ParserError
-          {}
+        flash = testable_flash(response)[flash_status]
+        if flash.kind_of?(Array)
+          if expecting.kind_of?(Array)
+            flash == expecting
+          else
+            matches = flash.select do |to_check|
+              to_check == expecting
+            end
+            matches.length > 0
+          end
+        else
+          flash == expecting
         end
-        cook[flash_status] =~ regex
       end
+
       match{|response| has_flash_cookie?(response)}
+
+      failure_message_for_should do |actual|
+        "expected that flash cookie :#{expected[0]} #{testable_flash(actual)[expected[0]]} would include #{expected[1].inspect}"
+      end
+      failure_message_for_should_not do |actual|
+        "expected that flash cookie :#{expected[0]} #{testable_flash(actual)[expected[0]]} would not include #{expected[1].inspect}"
+      end
     end
   end
 end

data/lib/cacheable_flash/test_helpers.rb

@@ -4,8 +4,15 @@ module CacheableFlash
   module TestHelpers
 
     def flash_cookie
-      return {} unless response.cookies['flash']
-      JSON(response.cookies['flash'])
+      return {} unless cooked_flash = response.cookies['flash']
+      JSON(cooked_flash)
+    rescue JSON::ParserError
+      {}
+    end
+
+    def testable_flash(response)
+      return {} unless cooked_flash = response.cookies['flash']
+      JSON(cooked_flash)
     rescue JSON::ParserError
       {}
     end

data/lib/cacheable_flash/version.rb

@@ -1,3 +1,3 @@
 module CacheableFlash
-  VERSION = "0.2.10"
+  VERSION = "0.3.0"
 end

data/spec/cacheable_flash/cacheable_flash_spec.rb

@@ -41,8 +41,8 @@ describe 'CacheableFlash' do
           @controller.write_flash_to_cookie
 
           expected_flash = {
-            'notice' => "Existing notice<br/>New notice",
-            'errors' => "Existing errors<br/>New errors",
+            'notice' => "New notice",
+            'errors' => "New errors",
           }
           JSON(@controller.cookies['flash']).should == expected_flash
         end
@@ -65,7 +65,7 @@ describe 'CacheableFlash' do
     it "converts flash value to string before storing in cookie if value is a number" do
       @controller.flash = { 'quantity' => 5 }
       @controller.write_flash_to_cookie
-      JSON(@controller.cookies['flash']).should == { 'quantity' => "5" }
+      JSON(@controller.cookies['flash']).should == { 'quantity' => 5 }
     end
     
     it "does not convert flash value to string before storing in cookie if value is anything other than a number" do
@@ -77,12 +77,19 @@ describe 'CacheableFlash' do
     it "encodes plus signs in generated JSON before storing in cookie" do
       @controller.flash = { 'notice' => 'Life, Love + Liberty' }
       @controller.write_flash_to_cookie
-#      puts "JSON::VERSION: #{JSON::VERSION}, #{JSON::VERSION >= "1.6"}"
-#      if JSON::VERSION >= "1.6"
-        @controller.cookies['flash'].should == "{\"notice\":\"Life, Love %2B Liberty\"}"
-#      else
-#        @controller.cookies['flash'].should == "{\"notice\": \"Life, Love %2B Liberty\"}"
-#      end
+      @controller.cookies['flash'].should == "{\"notice\":\"Life, Love %2B Liberty\"}"
+    end
+
+    it "escapes strings when not html safe" do
+      @controller.flash = { 'notice' => '<em>Life, Love + Liberty</em>' } # Not html_safe, so it will be escaped
+      @controller.write_flash_to_cookie
+      @controller.cookies['flash'].should == "{\"notice\":\"&lt;em&gt;Life, Love %2B Liberty&lt;/em&gt;\"}"
+    end
+
+    it "does not escape strings that are html_safe" do
+      @controller.flash = { 'notice' => '<em>Life, Love + Liberty</em>'.html_safe } # html_safe so it will not be escaped
+      @controller.write_flash_to_cookie
+      @controller.cookies['flash'].should == "{\"notice\":\"<em>Life, Love %2B Liberty</em>\"}"
     end
 
     it "clears the controller.flash hash provided by Rails" do

data/spec/dummy/app/controllers/dummy_controller.rb

@@ -1,22 +1,44 @@
 class DummyController < ApplicationController
+
   include CacheableFlash
+
   def index
-    expected_flash = {
-    'errors' => "This is an Error",
-    'notice' => "This is a Notice"
-    }
-    flash[:errors] = expected_flash['errors']
-    flash[:notice] = expected_flash['notice']
+    flash[:errors] = "This is an Error"
+    flash[:notice] = "This is a Notice"
   end
 
   def error
-    expected_flash = {
-    'errors' => "This is a real Error",
-    }
-    flash[:errors] = expected_flash['errors']
+    flash[:errors] << "Error ##{params[:id]}" # Cold boot the flash!
   end
 
   def no_flash
     # Does not set any flash
   end
+
+  def multiple_keys
+    flash[:notice] = 'This is a Notice'
+    flash[:errors] = 'This is an Error'
+    render :text => 'Foo'
+  end
+
+  def override
+    flash[:notice] = 'original'
+    flash[:notice] = 'message'
+    render :text => 'Foo'
+  end
+
+  def stack
+    flash[:notice] = 'original'
+    flash[:notice] << 'message'
+    flash[:notice] << 'another'
+    render :text => 'Foo'
+  end
+
+  def cold_boot
+    flash[:notice] << 'original'
+    flash[:notice] << 'message'
+    flash[:notice] << 'another'
+    render :text => 'Foo'
+  end
+
 end

data/spec/requests/integration_spec.rb

@@ -0,0 +1,58 @@
+require 'spec_helper'
+
+describe DummyController do
+
+  describe "cookie flash is sticky" do
+    it "should not clear after request" do # because they are only cleared out by javascripts
+      get "/dummy/index"
+      response.should have_flash_cookie('errors', "This is an Error")
+      response.should have_flash_cookie('notice', "This is a Notice")
+
+      get "/dummy/no_flash"
+      response.should have_flash_cookie('errors', "This is an Error")
+      response.should have_flash_cookie('notice', "This is a Notice")
+
+    end
+  end
+
+  describe "cookie flash is stackable" do
+    it "should not overwrite when new flash added" do # because they are only cleared out by javascripts
+      get "/dummy/index"
+      response.should have_flash_cookie('errors', "This is an Error")
+      response.should have_flash_cookie('notice', "This is a Notice")
+
+      get "/dummy/error?id=1"
+      response.should have_flash_cookie('errors', "This is an Error")
+      response.should have_flash_cookie('errors', "Error #1")
+
+      get "/dummy/error?id=2"
+      response.should have_flash_cookie('errors', "This is an Error")
+      response.should have_flash_cookie('errors', "Error #1")
+      response.should have_flash_cookie('errors', "Error #2")
+    end
+  end
+
+  # Stolen (and converted to a request spec) from stackable_flash:
+  #   https://github.com/pboling/stackable_flash/blob/master/spec/controllers/dummy_controller_spec.rb
+  it "should handle multiple keys" do
+    get "/dummy/multiple_keys"
+    response.should have_flash_cookie('notice', 'This is a Notice')
+    response.should have_flash_cookie('errors', 'This is an Error')
+  end
+
+  it "should override" do
+    get "/dummy/override"
+    response.should_not have_flash_cookie('notice','original')
+    response.should have_flash_cookie('notice','message')
+  end
+
+  it "should stack" do
+    get "/dummy/stack"
+    response.should have_flash_cookie('notice',['original','message','another'])
+  end
+
+  it "should cold boot" do
+    get "/dummy/cold_boot"
+    response.should have_flash_cookie('notice',['original','message','another'])
+  end
+end

data/spec/spec_helper.rb

@@ -4,6 +4,8 @@ require File.expand_path("../dummy/config/environment",  __FILE__)
 
 require 'rspec/rails'
 require "json"
+require 'cacheable_flash'
+require 'cacheable_flash/rspec_matchers'
 
 ENGINE_RAILS_ROOT=File.join(File.dirname(__FILE__), '../')
 
@@ -11,17 +13,16 @@ ENGINE_RAILS_ROOT=File.join(File.dirname(__FILE__), '../')
 # in spec/support/ and its subdirectories.
 Dir[File.join(ENGINE_RAILS_ROOT, "spec/support/**/*.rb")].each {|f| require f }
 
-require 'cacheable_flash'
-# Instead of loading the installed gem, we load the source code directly, would this work?
-#$LOAD_PATH.unshift(File.join(File.dirname(__FILE__), '..', 'lib'))
-#$LOAD_PATH.unshift(File.dirname(__FILE__))
-
-require 'cacheable_flash/rspec_matchers'
+RSpec.configure do |config|
+  config.treat_symbols_as_metadata_keys_with_true_values = true
+  config.run_all_when_everything_filtered = true
+  config.filter_run :focus
 
-# Requires supporting files with custom matchers and macros, etc,
-# in ./support/ and its subdirectories.
-#Dir["#{File.dirname(__FILE__)}/support/**/*.rb"].each {|f| require f}
+  # 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'
 
-RSpec.configure do |config|
   config.include CacheableFlash::RspecMatchers
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: cacheable_flash
 version: !ruby/object:Gem::Version
-  version: 0.2.10
+  version: 0.3.0
   prerelease: 
 platform: ruby
 authors:
@@ -13,13 +13,13 @@ cert_chain: []
 date: 2012-08-13 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
-  name: facets
+  name: stackable_flash
   requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 0.0.4
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -27,7 +27,7 @@ dependencies:
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: '0'
+        version: 0.0.4
 - !ruby/object:Gem::Dependency
   name: json
   requirement: !ruby/object:Gem::Requirement
@@ -83,7 +83,7 @@ dependencies:
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: 2.8.0
+        version: 2.11.0
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -91,7 +91,7 @@ dependencies:
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: 2.8.0
+        version: 2.11.0
 - !ruby/object:Gem::Dependency
   name: rdoc
   requirement: !ruby/object:Gem::Requirement
@@ -109,29 +109,13 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '3.12'
 - !ruby/object:Gem::Dependency
-  name: bundler
-  requirement: !ruby/object:Gem::Requirement
-    none: false
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: 1.0.24
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    none: false
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: 1.0.24
-- !ruby/object:Gem::Dependency
-  name: jeweler
+  name: reek
   requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: 1.6.4
+        version: 1.2.8
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -139,15 +123,15 @@ dependencies:
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: 1.6.4
+        version: 1.2.8
 - !ruby/object:Gem::Dependency
-  name: reek
+  name: roodi
   requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: 1.2.8
+        version: 2.1.0
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -155,15 +139,15 @@ dependencies:
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: 1.2.8
+        version: 2.1.0
 - !ruby/object:Gem::Dependency
-  name: roodi
+  name: rake
   requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: 2.1.0
+        version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
@@ -171,7 +155,7 @@ dependencies:
     requirements:
     - - ! '>='
       - !ruby/object:Gem::Version
-        version: 2.1.0
+        version: '0'
 description: ! 'Allows caching of pages with flash messages by rendering flash
 
   messages from a cookie using JavaScript, instead of statically in your Rails
@@ -212,7 +196,6 @@ files:
 - spec/cacheable_flash/install_spec.rb
 - spec/cacheable_flash/test_helpers_spec.rb
 - spec/controllers/dummy_controller_spec.rb
-- spec/dummy/README.rdoc
 - spec/dummy/Rakefile
 - spec/dummy/app/assets/javascripts/application.js
 - spec/dummy/app/assets/stylesheets/application.css
@@ -250,7 +233,7 @@ files:
 - spec/dummy/script/rails
 - spec/js_unit/cookie_test.html
 - spec/js_unit/flash_test.html
-- spec/requests/cacheable_flash_sticky_spec.rb
+- spec/requests/integration_spec.rb
 - spec/spec_helper.rb
 - tasks/cacheable_flash_tasks.rake
 - vendor/assets/javascripts/flash.js
@@ -286,7 +269,6 @@ test_files:
 - spec/cacheable_flash/install_spec.rb
 - spec/cacheable_flash/test_helpers_spec.rb
 - spec/controllers/dummy_controller_spec.rb
-- spec/dummy/README.rdoc
 - spec/dummy/Rakefile
 - spec/dummy/app/assets/javascripts/application.js
 - spec/dummy/app/assets/stylesheets/application.css
@@ -324,5 +306,5 @@ test_files:
 - spec/dummy/script/rails
 - spec/js_unit/cookie_test.html
 - spec/js_unit/flash_test.html
-- spec/requests/cacheable_flash_sticky_spec.rb
+- spec/requests/integration_spec.rb
 - spec/spec_helper.rb

data/spec/dummy/README.rdoc

@@ -1,261 +0,0 @@
-== 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
-  |   `-- tasks
-  |-- log
-  |-- public
-  |-- script
-  |-- test
-  |   |-- fixtures
-  |   |-- functional
-  |   |-- integration
-  |   |-- performance
-  |   `-- unit
-  |-- tmp
-  |   |-- cache
-  |   |-- pids
-  |   |-- sessions
-  |   `-- sockets
-  `-- vendor
-      |-- assets
-          `-- 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/spec/requests/cacheable_flash_sticky_spec.rb

@@ -1,31 +0,0 @@
-require 'spec_helper'
-
-describe DummyController do
-
-  describe "cookie flash is sticky" do
-    it "should not clear after request" do # because they are only cleared out by javascripts
-      get "/dummy/index"
-      response.should have_flash_cookie('errors', "This is an Error")
-      response.should have_flash_cookie('notice', "This is a Notice")
-
-      get "/dummy/no_flash"
-      response.should have_flash_cookie('errors', "This is an Error")
-      response.should have_flash_cookie('notice', "This is a Notice")
-
-    end
-  end
-
-  describe "cookie flash is stackable" do
-    it "should not overwrite when new flash added" do # because they are only cleared out by javascripts
-      get "/dummy/index"
-      response.should have_flash_cookie('errors', "This is an Error")
-      response.should have_flash_cookie('notice', "This is a Notice")
-
-      get "/dummy/error"
-      response.should have_flash_cookie('errors', "This is an Error")
-      response.should have_flash_cookie('errors', "This is a real Error")
-
-    end
-  end
-
-end