Chris Peters

I am about to commit some code that adds PostgreSQL JSON support for the `object`, `object_changes`, and `previous_draft` columns. After some thought about your issue, I don't think this change...

You're welcome and no problem. I just cut version 0.3.0 of the gem. I added support for PostgreSQL JSON because I needed to query some of the data within `draft#object`....

I figured out why this wasn't working. Draftsman calls `write_attribute` in several places, and that doesn't use the default accessor (in your case, `settings=`): http://www.davidverhasselt.com/set-attributes-in-activerecord/ I'm working on fixing another...

@jakehockey10 Thanks for reporting this, digging in further, and reporting your progress. I could see if it would be possible to add some logic that treats the deserialization differently if...

I'd have to look into it more, but perhaps `reify` could be modified to use ActiveRecord's reflection functionality to treat `inet` based attributes differently when deserializing.

@NullVoxPopuli I could see how this could be a problem with callbacks that fail. Are you able to give any specific example where this has been a problem for you?

@alexey I really hate to say this, but I would avoid nested attributes on models drafted with Draftsman. If you're interested, I could share a form model that I created...

@alexey I would like to see support for nested attributes added, but I must admit that I do not have the need for it personally. The app that I'm working...

I really don't see it being viable to add nested attribute support to Draftsman. These would be the 2 possible solutions that I can think of. (Maybe someone can propose...

@NullVoxPopuli Looks great. My favorite part of running an open source project like this is being schooled by contributors. :) I'll sit on this one little bit and think about...