Sha256: 1148784e3a57f4f8144b71e24657b7367e8aa8e09589a94ae372dbbc6068f35f
Contents?: true
Size: 1.18 KB
Versions: 2
Compression:
Stored size: 1.18 KB
Contents
=== Upgrade to rspec-rails-1.1.99.4 == update generated files Be sure to run "script/generate rspec" and allow the following files to be overwritten: * lib/tasks/rspec.rake * script/spec_server == route_for After a change to edge rails broke our monkey-patched #route_for method, I decided to just delegate to rails' #assert_generates method. For most cases, this will not present a problem, but for some it might. You'll know if you upgrade and see any newly failing, route-related examples. Here are the things that you might need to change. * Make sure IDs are strings If you had :id => 1 before, you need to change that to :id => "1" #old route_for(:controller => 'things', :action => 'show', :id => 1).should == "/things/1" #new route_for(:controller => 'things', :action => 'show', :id => "1").should == "/things/1" * Convert paths for non-get methods to hashes If you had an example with a route that requires post, put, or delete, you'll need to declare that explicitly. #old route_for(:controller => 'things', :action => 'create').should == "/things" #new route_for(:controller => 'things', :action => 'create').should == {:path => "/things", :method => :post}
Version data entries
2 entries across 2 versions & 1 rubygems
Version | Path |
---|---|
dchelimsky-rspec-rails-1.1.99.4 | Upgrade.txt |
dchelimsky-rspec-rails-1.1.99.5 | Upgrade.txt |