consider linking to my attr_json gem too?

[jrochkind]

Hi, this is neat! I've used a similar approach with Rails Attributes API, in a somewhat different direction, in attr_json.

I see you link in the README to store_attribute and jsonb_accessor, would you consider linking to attr_json too?

Currently attr_json meets a somewhat different use case than store_accessor: I wanted to store both arrays of primitives and models in a single json column, to sort of give you some embedded "NoSQL"-like functionality in an activerecord. I also wanted to support nested models (a model can include other models as an attribute), and convenient support for using rails form builder (or simple_form) with all your embedded/nested models.

attr_json doesn't at the moment support the particular use case of store_model, with a single model that maps to an entire json column (instead attr_json wants it to map to a key in a hash in a json column). It might in the future though, it's been asked for.

I wonder if there's a way for us to collaborate/join forces, but also think it's not too much of a problem that we both are doing our thing, that's how innovation and experimentation works! I think it's neat that the Rails Attribute API allows us to do these things!

[DmitryTsepelev]

Hi @jrochkind, sorry for being so slow to reply! 😅

I see you link in the README to store_attribute and jsonb_accessor, would you consider linking to attr_json too?

Sure thing, hopefully you could make a link to me too

but also think it's not too much of a problem that we both are doing our thing

Completely agreed - the main common thing between our gems is that we use JSON DB column as a storage while solving different goals

[jrochkind]

Hi, I have linked to store_model in the attr_json README!

I think it's possible we might be pursuing quite similar or even the same goals. But we'll see how it all works out!