This project is archived and is in readonly mode.
Defining routes with symbols failes
-
iGEL
- Tag changed from 2.1, actionpack, routing to 2.1, actionpack, routing
Since I couldn't think of a way to test the solution described above, I found another one. The :controller and :action are now converted to a string, if they were a symbol before. Test is included.
-
Pratik
- Tag changed from 2.1, actionpack, routing to 2.1, actionpack, patch, routing
- Assigned user set to Michael Koziarski
-
CancelProfileIsBroken
Patch doesn't apply cleanly on current edge. Would be easy enough to fix up the patch, but...I don't think I see a good reason to do this. Not every API that accepts strings needs to automatically accept symbols in their place.
-
iGEL
Well, I don't need to define routes with symbols, but I think, if I cannot do so, there should be an exception or something. Rendering the view without executing the action is not an expectable behavior...
-
Michael Koziarski
I agree with mike that we shouldn't always make every api symbol or string agnostic. However the silent failure is a problem here.
Another comment is that looping over options is wasteul if you're only checking two values. You should just convert those two known keys.
-
CancelProfileIsBroken
- State changed from new to incomplete
Should resubmit with the requested changes if you still want this.
-
CancelProfileIsBroken
- Tag changed from 2.1, actionpack, patch, routing to 2.1, actionpack, bugmash, patch, routing
-
Rizwan Reza
not reproducible
-1 This is already fixed. Just checked in 2-3-stable and master.
-
Arthur Zapparoli
not reproducible
-1 it works on 2-3-stable
-
Michael Koziarski
- State changed from incomplete to resolved
-
Michael Koziarski
- Tag changed from 2.1, actionpack, bugmash, patch, routing to 2.1, actionpack, patch, routing
