I added them because I wasn't able to test calling
ActivitiesController#milestone with the :chapter because
ActionController::TestCase seems to automatically to_s all of the params.

Manual testing and the explicit routing tests do the same thing both with
and without the duplicate routes.

Duplicate routes should not affect actual functionality...

It does not affect matching because the "old" route will match first.
(rails is ok with duplicate routes, it needs to be because of all the
wildcard stuff)

It does not affect generating because those routes are only generatable as
named routes (and the new ones do not have names).

It does feel a bit wrong to have something like this for only tests, so I
tried to hack the tests or the test framework itself, but I couldn't make
anything work.


On Tue, Apr 15, 2014 at 12:06 PM, tobyk100 <notifications@github.com> wrote:

> In config/routes.rb:
>
> > @@ -66,14 +66,23 @@
> >    get 'reset_session', to: 'application#reset_session_endpoint'
> >
> >    get '/hoc/reset', to: 'script_levels#show', script_id: Script::HOC_ID, reset:true, as: 'hoc_reset'
> > +  get '/hoc/reset', to: 'script_levels#show', script_id: Script::HOC_ID.to_s, reset:true
>
> How do these repeat routes work?
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/code-dot-org/dashboard/pull/470/files#r11651843>
> .
>