Regarding: http://dev.rubyonrails.org/ticket/4433
I created a small patch for this ticket that makes an association's
owner and reflection available to code in extensions. I'd like to
get some feedback on the approach I took and some indication as to
whether this might be accepted into the trunk at some point. While
it's not critical for my work, it would sure make some things a lot
simpler.
Also: http://dev.rubyonrails.org/ticket/4769
This is related to #4433. Someone on the email list ran into this
problem, and while I was working on #4433 I kept wondering about the
issue. When building a proxy wrapper class you don't want to block
any methods on the target object that people might want to use.
Unfortunately that's what's happening here. It might be useful to
consider what to do about this in conjunction with #4433 so that we
can get some consistency.
"You can be consistent, or you can be inconsistent, but you can't be
both." -- Kent Beck, 1988
--
Josh Susser
http://blog.hasmanythrough.com
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
