rails/journey — comment on commit 70d101b3386ba26ff801cec496da9c23389434aa
File:  line 0
By cgunther:

I'm seeing a similar regression after upgrading from v1.0.1 to v1.0.2, however it only affects my tests

```
ActionController::RoutingError:
No route matches {:action=>"show", :controller=>"accessory/items", :id=>#}
```

The line triggering that is:

``` ruby
redirect_to accessory_item_path(@item)
```

Clipped rake routes:

```
accessory_item GET /accessory/items/:id(.:format) accessory/items#show
```

Clipped routes.rb

``` ruby
namespace :accessory do
resources :items, only: [:show, :new, :create, :edit, :update] do
get 'activate', on: :member
end
end
```

I have the `#find` calls stubbed out in this test to avoid hitting the database and it returns un-persisted model instances, which `#to_param` returns `nil` on.

I realize that my tests may have been falsely passing before this v1.0.2 update, but it is a regression nevertheless and wanted to get the official opinion on it.