ruby on rails - Does it make sense to use cocoon solely for a has_one relationship? -

i've been trying cocoon working form handles has_one relationship no has_many relationships, , come across few gotchas, such cocoon , has_one association .

i'm starting wonder if i'm taking wrong approach using cocoon in scenario. 1 reason documentation cocoon talks has_many relationships, not has_one ones. maybe it's because benefits cocoon when there's has_many relationship , want dynamically create related objects.

is cocoon supposed make relationships easier in way that's useful has_one relationships?

in opinion cocoon not useful has_one relationship. note when create fields_for association have first field generated default. if have has_many relation , need add more of may use cocoon. has_one relationship normal rails form trick.

coocon doesn't make relationships easier rather adding multiple assoicated objects @ same time form made easier using that.

hope helps.