Draftpunk w/ Amoeba Gem

Hi Steve,

I finally got time to try your gem, and after adding it to my project, now my app fails its tests regarding our duplicate methods. Could it be due to the fact your gem uses Amoeba gem too?

[stevehodges]

Draft punk relies on amoeba configurations for approvable models and their child associations. So, if you're already using amoeba on those models, it's quite likely we'll see conflicts (or outright bizarre behavior). Out of curiousity, what amoeba configurations are you using on those models? I wonder if there are more options draft_punk should support which could be passed through to amoeba

It seems Amoeba overrides our configuration. The problem is that our structure and duplicate is quite special and complex. It fails validation when we use draftpunk at the moment.

One thing you could use is it Amoeba on the fly configuration. That would solve the problem that the "local amoeba configuration" still works.

Then to answer your question, we are using:

• nullify 5 times

• prepend 4 times

• set 5 times

• propagate 1 time

  • We have a unique attribute in every single model we need to set it to nil, so we use propagate coupled with nullify

• include_association 2 times

• exclude_association 4 times

• recognize + exclude_association (different behaviour) 3 times

• customize 1 time