I've
written an ActiveRecord extension that allows Associations to be
automatically generated at runtime without requiring "has_many" and
"belongs_to" to be defined in the class.
The use of has_many vs has_one is determined by the pluralisation of the method call.Additionally, it uses the :null =>
David Heinemeier Hansson wrote:
So...is this intentional? Would core be open to a patch that allowed AR
to differentiate between "nil -- this association needs to be loaded"
and "nil -- the target is actually nil"?
Yes, please do investigate something better. I believe it was done
simply becaus
On 8/8/06, Michael A. Schoen <[EMAIL PROTECTED]> wrote:
David Heinemeier Hansson wrote:
>> So...is this intentional? Would core be open to a patch that allowed AR
>> to differentiate between "nil -- this association needs to be loaded"
>> and "nil -- the target is actually nil"?
>
> Yes, please d
Hello,
Just thought I'd make a remark regarding documentation.
The submission process for patches doesn't mention updating associated
documentation (as far as I can see). This should also be a
requirement along with test cases so that documentation stays up to
date. If we're planning on having
Andrew Kaspick wrote:
The submission process for patches doesn't mention updating associated
documentation (as far as I can see). This should also be a
requirement along with test cases so that documentation stays up to
date. If we're planning on having good documention and we use the
fund mo
I think at the moment it's heavily encouraged that documenation be
included with patches. What this turns out to mean commit side is that
if your patch has associated documentation and tests included it's
significantly more likely that it will be commited. More people just
need to know this (or ta
On Aug 8, 2006, at 10:41 AM, Andrew Kaspick wrote:
The submission process for patches doesn't mention updating associated
documentation (as far as I can see). This should also be a
requirement along with test cases so that documentation stays up to
date.
+1
court3nay
___
Another good example that lacks documentation is behavior
additions/changes. I.e.: the patch for has_one saving on create versus
saving on update where it used to save on both. The new patch doesn't
do what I expect and I has to bug poor Jonathan to clarify what his
expectations were on his p
For example I just submitted a documentation patch
(http://dev.rubyonrails.org/ticket/5762) for the :from option for the
ActiveRecord find method. I'd think that adding support for this
option should have had documentation associated with it when it was
added to begin with.
Just me 2 cents.
Tr
On Aug 8, 2006, at 3:47 PM, Michael Koziarski wrote:
For example I just submitted a documentation patch
(http://dev.rubyonrails.org/ticket/5762) for the :from option for the
ActiveRecord find method. I'd think that adding support for this
option should have had documentation associated with it w
10 matches
Mail list logo
