Hassan Zamani
Hassan Zamani
It is a bug. And PR is welcome :-)
Best way seems to have a 'acts-as-relation-compatibility' gem and add compatibility features there. However it don't seem to be a good idea to merge these features here, isn't it?
You can use names as in `references` migration method with `:as` option. For example: ``` ruby actable as: :some_name ``` will produce `some_name_id` and `some_name_type` columns. There is not any...
Why there should be such a circular dependency in model?
A game is a node an belongs to another node? Even if this is the case, polymorphic makes no sense. We usually don't use a model name as a polymorphic...
Maybe it's to late! But why `polymorphic: true` is there?
Maybe it's better to not override `is_a?`
What about changing primary key on acting_as models? After that `id` would resolve to actable model.
That highly depends on your app, but nothing prevents that.
we currently do not support `rails 3`, patches are welcome