Integrating with acts_as_list about draftsman HOT 2 CLOSED

Draftsman will not handle these types of ActiveRecord callbacks where the database is updated directly without interacting with the model, which is a downfall. I'm finding that drafts make everything harder. :)

In my app, I've had to create a draft_position column and manage it manually through a form object. I also handle publishing through a service object, which sorts out a published position column based on the drafts being published. Once you get a handle on form and service objects, you'll find that they're the best way to get through some of these more complex draft situations.

Another option is to just not record drafts for a sort order column. I know that's probably not a good answer though.

Let me know if you have any specific questions. I'll continue to think about how this gem can be friendlier, but I think this sort of stuff is where ActiveRecord starts to draw criticism.

from draftsman.

Thanks Chris, totally makes sense. I think we're going to do something similar with drafts and position. We're still undecided if acts_as_list is helping or hurting us right now, so we might be dropping it in favor of using our own positioning :)

draftsman is pretty friendly already -- I was just curious how you're handling it. If I come up with something different, I'll let you know.

Thanks for the reply!

from draftsman.