Document what actions are made available in an anonymous controller #415

Merged
merged 1 commit into from Dec 20, 2011

Projects

None yet

4 participants

@alanshields

It's a somewhat long test, but it shows what calls you can make and
what calls you cannot make on an anonymous controller. I ran into this
issue myself when I thought that all actions were routed.

They weren't.

Written on time paid for by onetotheworld.net

@alanshields alanshields Document what actions are made available in an anonymous controller
It's a somewhat long test, but it shows what calls you can make and
what calls you cannot make on an anonymous controller. I ran into this
issue myself when I thought that all actions were routed.

They weren't.

Written on time paid for by onetotheworld.net
c8523df
@jdelStrother

The fact it only sets up routes for the regular index/show/create/update/destroy caught me off guard too : is this really desired behaviour, or would it be better to set up the routes to match any controller action that happens to be specified?

@alanshields

If someone wouldn't mind taking a look at this. I find I keep referring back to this code when doing anonymous controller work. That would indicate to me, at least, that this is good documentation. Though since I'm the one who wrote it, maybe not.

@travis
travis commented Nov 3, 2011

+1 on this - definitely confusing as is

@dchelimsky dchelimsky merged commit b8b6f79 into rspec:master Dec 20, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment