Kostiantyn Stepaniuk

Thanks for opening an issue. @andrefy @anke1460 do you think you can and have enough time to contribute to this gem? I'm looking for a person who I can give...

Not sure if I understood you correctly. All attributes are assigned only to one entity (Product, Category, etc). Please, look at [attribute name index](https://github.com/kostyantyn/hydra_attribute/blob/master/lib/hydra_attribute/migrator.rb#L75). It allows to create attribute `signing_date`...

i've got it. it's a good idea. I can create a separate `hydra_entities` table where `Car` and `TV` will be stored and attach all attributes to these entities instead of...

I don't know the day of the next release because I'm so busy now but i'll try to make a time and do it. Currently, the most of code from...

I think it's a good idea to create a new set based on another one or merge. I'll think about implementation it but it will not be added in the...

I've already thought about this feature. Maybe it will be supported, but after the first stable version is released.

As I understand, attachment type is a combination of several string and integer types, so it's supported out of box. I haven't tested hydra_attribute with other popular gems like paperclip,...

I am going to merge "value_model_optimization" branch into master in the next two weeks, there are a big refactoring and performance improvements. So, maybe you should look at that code....

yes, I am planning to extend the list of backend types, which are supported by sqlite, mysql and postgresql, in the next release. Maybe, I'll add some specific postgresql datatypes...

Yes, I am planning to add them. Validations will be stored in hydra_attributes table like other meta-information and the API will be the following: ``` ruby Product.hydra_attributes.create(name: '...', presence: true)...