Problematic Resources nested in Models
Reported by Carl Porth | May 28th, 2009 @ 07:51 PM
Associations don't correctly use resources when they are nested in a module.
Example: http://gist.github.com/119699
Comments and changes to this ticket
-
Dan Kubb (dkubb) May 28th, 2009 @ 07:53 PM
- State changed from “unconfirmed” to “accepted”
- Assigned user set to “Dan Kubb (dkubb)”
-
Dan Kubb (dkubb) May 28th, 2009 @ 08:17 PM
Carl, could you try the following patch and let me know if it resolves your problem? http://gist.github.com/119711
-
-
Dan Kubb (dkubb) May 28th, 2009 @ 09:37 PM
- State changed from “accepted” to “resolved”
(from [2776df23c827f6910c8677c3e3821d532a33a9ba]) Demodulize the source model name for inverse relationship names
- Updated resource and collection related scripts to use namespaced models to ensure they work perfectly.
[#869 state:resolved] http://github.com/datamapper/dm-core/commit/2776df23c827f6910c8677c...
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 »
People watching this ticket
Carl Porth
Dan Kubb (dkubb)
Tags
Referenced by
-
869
Problematic Resources nested in Models
[#869 state:resolved]
http://github.com/datamapper/dm-co...