Chris Roos's profile - rails

Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Chris Roos's latest activity

Wednesday, May 20 2009

2682 Vendorised gems (e.g. rspec-rails) not recognised as being installed was updated in Ruby on Rails

- Tag changed from gem, gem_dependency, rspec_rails to gem, gem_dependency, rspec_rails, verified
by Chris Roos at 3:37 PM
Chris Roos created the ticket at 3:08 PM
I've got rspec and rspec-rails unpacked in vendor/gems and the dependencies defined in environments/test.rb (as specified here[1]). I checked out my project to ...

Friday, September 26 2008

~~144~~ ~~Bug in Rails Route Globbing~~ was updated in Ruby on Rails

Chris Roos commented at 3:07 PM
"It turns out that Rails is now breaking RFC 2396 http://www.ietf.org/rfc/rfc2396.txt (see section 3.3). << Within a path segment, the characters "/", ";", "=",...

Wednesday, August 20 2008

700 ActionMailer::Base should respond to methods handled by method_missing was updated in Ruby on Rails

Chris Roos commented at 10:01 AM
1. The current implementation generates a lot of unnecessary noise when you disable the stubbing of non existent methods in Mocha.

Wednesday, May 21 2008

144 [PATCH] Bug in Rails Route Globbing was updated in Ruby on Rails

Chris Roos commented at 9:33 AM
Personally, I'd probably avoid adding a special case with the defence that the added complexity isn't warranted. In my opinion, supplying the path components ...

Friday, May 09 2008

144 [PATCH] Bug in Rails Route Globbing was updated in Ruby on Rails

Chris Roos commented at 9:30 AM

Here's an attempt at an explanation...

At a really basic level, the current implementation escapes too late. The array of *additional values is turned into a...

Thursday, May 08 2008

144 [PATCH] Bug in Rails Route Globbing was created in Ruby on Rails

Chris Roos created the ticket at 4:55 PM

Slashes in the 'globbed' parameters are not escaped. The patch contains two modified tests, to illustrate the bug, and a fix.

Given this route:

map.connect ...