singleton spec shouldn;t have a key
Reported by Ian White | September 29th, 2009 @ 08:31 AM
[submitted on behalf of Sergei Serdyuk]
If I declare a resource both as a singleton and a regular,
'map_enclosing_resource' for the singleton resource breaks wildcard
loading for the regular. The reason is that singleton
specifications have keys identical to regular specifications and
those collide. As it was not clear to me why singleton
specifications need keys at all, I've added the following to
SingletonSpecification#initialize and that fixed it for me.
options[:key] ||= ''
Comments and changes to this ticket
-
Ian White September 29th, 2009 @ 08:47 AM
- State changed from “new” to “resolved”
(from [0376d1035f86e814553eaab7036ec3ead0ae331c]) Make sure that singleton spec has no key [#5 state:resolved] http://github.com/ianwhite/resources_controller/commit/0376d1035f86...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
resources_controller is a rails plugin that eases the pain of RESTful controllers.
People watching this ticket
Ian White
Referenced by
-
5
singleton spec shouldn;t have a key
(from [0376d1035f86e814553eaab7036ec3ead0ae331c])
Make su...