Topic: Backport of custom routes anti-vinegar

Now that Edge no longer enforces vinegar for custom RESTful routes, has anyone heard word of back port to Rails 1.2? I'm deploying a very time-sensitive app (no time for debugging errors on Edge), but would really like to ditch the ugly semicolons in my custom routes.

If a back port hasn't been done yet, does anyone know how involved it would be?

I thought about how mothers feed their babies with tiny little spoons and forks, so I wondered what do Chinese mothers use. Toothpicks?

Re: Backport of custom routes anti-vinegar

It looks like there were only a couple of lines changed to remove the semicolons. Could this be implemented with a monkey patch?

I thought about how mothers feed their babies with tiny little spoons and forks, so I wondered what do Chinese mothers use. Toothpicks?

Re: Backport of custom routes anti-vinegar

Look into the simply_restful plugin for some examples of monkey-patching routes. Looks like you just need to add the semicolon routes back. Just don't make them named routes so there's no conflict.

Also, I recommend submitting a ticket about this if there isn't one already. I know I would want it in my apps when I make the move.

Railscasts - Free Ruby on Rails Screencasts