blocks|key|468073|text|我认为这应该行得通：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|468074|FactoryGirl.define+do
++factory+:relationship+do+
++++association+:guardian
++++relationship_type+RelationshipType.first
++++after_build+do+%7Crelationship%7C
++++++relationship.student+=+Factory(:student,+:school+=>+relationship.guardian.school)
++++end
++end
end|code-block|syntax|javascript|468075|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I think this should work:

<pre><code>FactoryGirl.define do
 factory :relationship do 
 association :guardian
 relationship_type RelationshipType.first
 after_build do |relationship|
 relationship.student = Factory(:student, :school =&gt; relationship.guardian.school)
 end
 end
end
</code></pre>

blocks|key|468135|text|这个答案是谷歌上“工厂女孩分享协会”的第一个结果，来自santuxus的答案真的帮了我很大的忙:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|468136|下面是最新版本的Factory+Girl的语法更新，以防其他人偶然发现：|468137|FactoryGirl.define+do
++factory+:relationship+do
++++guardian
++++relationship_type+RelationshipType.first

++++after(:build)+do+%7Crelationship%7C
++++++relationship.student+=+FactoryGirl.create(:student,+school:+relationship.guardian.school)+unless+relationship.student.present?
++++end
++end
end|code-block|syntax|javascript|468138|unless子句防止student在与FactoryGirl.create(:relationship,+student:+foo)一起传入工厂时被替换。|offset|length|style|CODE|468139|entityMap^0|0|0|0|0|6|A|7|J|1B|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]|$K|W|L|X|M|N]|$K|Y|L|Z|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|P|$]]

This answer is the first result on Google for 'factory girl shared association' and the answer from santuxus really helped me out :)

Here's an update with the syntax from the latest version of Factory Girl in case anyone else stumbles across it:

<pre><code>FactoryGirl.define do
 factory :relationship do
 guardian
 relationship_type RelationshipType.first

 after(:build) do |relationship|
 relationship.student = FactoryGirl.create(:student, school: relationship.guardian.school) unless relationship.student.present?
 end
 end
end
</code></pre>

The <code>unless</code> clause prevents <code>student</code> from being replaced if it's been passed into the factory with <code>FactoryGirl.create(:relationship, student: foo)</code>.

blocks|key|684166|text|有一种更清晰的方式来编写这种关联。从this+github+issue那里得到了答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|684167|FactoryGirl.define+do
++factory+:relationship+do+
++++association+:guardian
++++student+{+build(:student,+school:+relationship.guardian.school)+}
++++relationship_type+RelationshipType.first
++end
end|code-block|syntax|javascript|684168|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/thoughtbot/factory_girl/issues/426^0|I|H|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

There is cleaner way to write this association. Answer got from <a href="https://github.com/thoughtbot/factory_girl/issues/426" rel="nofollow">this github issue</a>.

<pre><code>FactoryGirl.define do
 factory :relationship do 
 association :guardian
 student { build(:student, school: relationship.guardian.school) }
 relationship_type RelationshipType.first
 end
end
</code></pre>

blocks|key|468198|text|这并不是您真正想要的答案，但似乎创建此关联的困难在于建议可能需要调整表设计。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|468199|询问问题What+if+the+user+changes+school?时，Student和Guardian上的学校都需要更新，否则，模型将不同步。|offset|length|style|CODE|468200|我提出一个学生，一个监护人，一个学校，都是有关系的。如果学生换了学校，则会为新学校创建一个新的Relationship。作为一个很好的副作用，这使得学生在哪里接受教育的历史得以存在。|468201|belongs_to关联将从Student和Guardian中删除，并改为移动到Relationship。|468202|然后，可以将工厂更改为如下所示：|468203|factory+:relationship+do
++school
++student
++guardian
++relationship_type
end|code-block|syntax|javascript|468204|然后可以通过以下方式使用它：|468205|#+use+the+default+relationship+which+creates+the+default+associations
relationship+=+Factory.create+:relationship
school+=+relationship.school
student+=+relationship.student
guardian+=+relationship.guardian

#+create+a+relationship+with+a+guardian+that+has+two+charges+at+the+same+school
school+=+Factory.create+:school,+name:+'Custom+school'
guardian+=+Factory.create+:guardian
relation1+=+Factory.create+:relationship,+school:+school,+guardian:+guardian
relation2+=+Factory.create+:relationship,+school:+school,+guardian:+guardian
student1+=+relation1.student
student2+=+relation2.student|468206|entityMap^0|0|4|W|12|7|1A|8|0|1B|C|0|0|A|E|7|M|8|14|C|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]|$D|12|E|13|F|G]|$D|14|E|15|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@$D|17|E|18|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|19|8|@$D|1A|E|1B|F|G]|$D|1C|E|1D|F|G]|$D|1E|E|1F|F|G]|$D|1G|E|1H|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1I|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|1J|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|1K|8|@]|9|@]|A|$]]|$1|U|3|V|5|P|7|1L|8|@]|9|@]|A|$Q|R]]|$1|W|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|X|$]]

This isn't really an answer you are seeking, but it seems that the difficulty in creating this association is suggesting that the table design may need to be adjusted.

Asking the question <code>What if the user changes school?</code>, the school on both the <code>Student</code> and <code>Guardian</code> needs to be updated, otherwise, the models get out of sync.

I put forward that a student, a guardian, and a school, all have a relationship together. If a student changes school, a new <code>Relationship</code> is created for the new school. As a nice side effect this enables a history to exist of where the student has been schooled.

The <code>belongs_to</code> associations would be removed from <code>Student</code> and <code>Guardian</code>, and moved to <code>Relationship</code> instead.

The factory can then be changed to look like this:

<pre><code>factory :relationship do
 school
 student
 guardian
 relationship_type
end
</code></pre>

This can then be used in the following ways:

<pre><code># use the default relationship which creates the default associations
relationship = Factory.create :relationship
school = relationship.school
student = relationship.student
guardian = relationship.guardian

# create a relationship with a guardian that has two charges at the same school
school = Factory.create :school, name: 'Custom school'
guardian = Factory.create :guardian
relation1 = Factory.create :relationship, school: school, guardian: guardian
relation2 = Factory.create :relationship, school: school, guardian: guardian
student1 = relation1.student
student2 = relation2.student
</code></pre>

blocks|key|684253|text|在本例中，我将使用transient+&+dependent属性：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|684254|FactoryGirl.define+do
++factory+:relationship+do
++++transient+do
++++++school+{+create(:school)+}
++++++#+now+you+can+even+override+the+school+if+you+want!
++++end

++++guardian+{+create(:guardian,+school:+school)+}
++++student+{+create(:student,+school:+school)+}
++++relationship_type+RelationshipType.first
++end
end|code-block|syntax|javascript|684255|用法：|684256|relationship+=+FactoryGirl.create(:relationship)

relationship.guardian.school+==+relationship.student.school
#+=>+true|684257|如果你愿意，你甚至可以覆盖学校：|684258|awesome_school+=+FactoryGirl.create(:school)
awesome_relationship+=+FactoryGirl.create(:relationship,+school:+awesome_school)

awesome_relationship.guardian.school+==+awesome_school
#+=>+true
awesome_relationship.student.school+==+awesome_school
#+=>+true|684259|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/thoughtbot/factory_girl/blob/master/GETTING_STARTED.md#transient-attributes|1|https://github.com/thoughtbot/factory_girl/blob/master/GETTING_STARTED.md#dependent-attributes^0|9|9|0|L|9|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]|$A|14|B|15|1|16]]|C|$]]|$1|D|3|E|5|F|7|17|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|18|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|19|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|1A|8|@]|9|@]|C|$]]|$1|O|3|P|5|F|7|1B|8|@]|9|@]|C|$G|H]]|$1|Q|3|-4|5|6|7|1C|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]|Y|$5|T|U|V|C|$W|Z]]]]

I'd use <a href="https://github.com/thoughtbot/factory_girl/blob/master/GETTING_STARTED.md#transient-attributes" rel="nofollow noreferrer">transient</a> &amp; <a href="https://github.com/thoughtbot/factory_girl/blob/master/GETTING_STARTED.md#dependent-attributes" rel="nofollow noreferrer">dependent</a> attributes in this case:

<pre><code>FactoryGirl.define do
 factory :relationship do
 transient do
 school { create(:school) }
 # now you can even override the school if you want!
 end

 guardian { create(:guardian, school: school) }
 student { create(:student, school: school) }
 relationship_type RelationshipType.first
 end
end
</code></pre>

Usage:

<pre><code>relationship = FactoryGirl.create(:relationship)

relationship.guardian.school == relationship.student.school
# =&gt; true
</code></pre>

And you can even override the school if you want:

<pre><code>awesome_school = FactoryGirl.create(:school)
awesome_relationship = FactoryGirl.create(:relationship, school: awesome_school)

awesome_relationship.guardian.school == awesome_school
# =&gt; true
awesome_relationship.student.school == awesome_school
# =&gt; true
</code></pre>

blocks|key|684332|text|在nitsas的解决方案上进行扩展，您可以滥用@overrides检查监护人或学生协会是否已被覆盖，并使用来自监护人/学生的学校协会。这使您不仅可以覆盖学校，而且还可以覆盖监护人或学生。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|684333|不幸的是，这依赖于实例变量，而不是公共API。未来的更新很可能会毁掉你的工厂。|684334|factory+:relationship+do
++guardian+{+create(:guardian,+school:+school)+}
++student++{+create(:student,++school:+school)+}

++transient+do
++++school+do
++++++if+@overrides.key?(:guardian)
++++++++guardian.school
++++++elsif+@overrides.key?(:student)
++++++++student.school
++++++else
++++++++create(:school)
++++++end
++++end
++end
end|code-block|syntax|javascript|684335|entityMap^0|N|A|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Extending on nitsas' solution, you can abuse <code>@overrides</code> to check whether the guardian or student association have been overridden, and use the school association from the guardian/student. This allows you to override not only the school, but also just the guardian or just the student.

Unfortunately, this relies on instance variables, not public API. Future updates could very well break your factories.

<pre class="lang-ruby prettyprint-override"><code>factory :relationship do
 guardian { create(:guardian, school: school) }
 student { create(:student, school: school) }

 transient do
 school do
 if @overrides.key?(:guardian)
 guardian.school
 elsif @overrides.key?(:student)
 student.school
 else
 create(:school)
 end
 end
 end
end
</code></pre>

I've got these 5 models: Guardian, Student, Relationship, RelationshipType and School. Between them, I've got these associations

<pre><code>class Guardian &lt; ActiveRecord::Base
 belongs_to :school
 has_many :relationships, :dependent =&gt; :destroy
 has_many :students, :through =&gt; :relationships
end

class Student &lt; ActiveRecord::Base
 belongs_to :school
 has_many :relationships, :dependent =&gt; :destroy
 has_many :guardians, :through =&gt; :relationships
end

class Relationship &lt; ActiveRecord::Base
 belongs_to :student
 belongs_to :guardian
 belongs_to :relationship_type
end

class School &lt; ActiveRecord::Base
 has_many :guardians, :dependent =&gt; :destroy
 has_many :students, :dependent =&gt; :destroy
end

class RelationshipType &lt; ActiveRecord::Base
 has_many :relationships
end
</code></pre>

I want to write a FactoryGirl which defines a relationship. Every relationship must have a guardian and a student. These two must belong to the same school. The guardian factory has an association with school, and so does the student factory. I've been unable to get them to be built in the same school. I've got the following code:

<pre><code>FactoryGirl.define do

 factory :relationship do
 association :guardian
 association :student, :school =&gt; self.guardian.school
 relationship_type RelationshipType.first
 end

end
</code></pre>

This results in the following error when I try to build a relationship using this factory:

<pre><code>undefined method `school' for #&lt;FactoryGirl::Declaration::Implicit:0x0000010098af98&gt; (NoMethodError)
</code></pre>

Is there any way to do what I want, to make the guardian and the student belong to the same school without having to resort to passing already created guardians and students to the factory (which is not its purpose)?

Get two associations within a Factory to share another association

我有这5个模型:卫报，学生，关系，RelationshipType和学校。在他们之间，我有这些联想class Guardian < ActiveRecord::Base belongs_to :school has_many :relationships, :dependent => :destroy has_m...

问让工厂中的两个关联共享另一个关联
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问让工厂中的两个关联共享另一个关联EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问让工厂中的两个关联共享另一个关联
EN