method not found in collection when defined using module and not directly in class
Reported by gucki | May 21st, 2010 @ 05:11 AM
If you define a class method directly like
it works.
But if you define the class method in a module and mixit in like this
it fails.
I guess dm somehow copies the class methods inside the collection and misses this step when extend is used..?!
Comments and changes to this ticket
-
gucki May 21st, 2010 @ 05:33 AM
Ok this seems to only fail when using ruby 1.9.2:
ruby 1.9.2dev (2010-05-15 revision 27800) [x86_64-linux]
ruby 1.9.2dev (2010-05-21 revision 27947) [x86_64-linux]Works fine with ruby 1.8.7 (ree 2010.1).
-
Dan Kubb (dkubb) May 22nd, 2010 @ 12:57 AM
- State changed from “new” to “resolved”
(from [acd2f5c12d6e6f8d2cd1bddb9c0ff58705dbcb44]) Simplified logic to determine if a model/resource method exists
[#1282 state:resolved] http://github.com/datamapper/dm-core/commit/acd2f5c12d6e6f8d2cd1bdd...
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
gucki
Referenced by
-
1282
method not found in collection when defined using module and not directly in class
[#1282 state:resolved]
http://github.com/datamapper/dm-c...