Support Polymorphic Associated Objects: Take 2

[kaspth]

In #25, we discussed how to have Polymorphic Associated Objects and we ultimately ruled that it was better to share code via concerns.

I tried a slightly alternate approach, but I'm still coming to the same conclusion: trying to remove/defer the connection to an Active Record class opens up a whole bunch of complexity. E.g. extension blocks needs to be captured and then applied when the actual connection happens.

So I'm opening this just for reference and I'm closing it immediately in favor of writing up the concerns approach.

[kaspth]

Still thinking of trying to have something like this:

class Pricing < ActiveRecord::AssociatedObject::Polymorphic
end

class Post::Pricing < Pricing
end

Where Polymorphic would be a slimmed down interface. Really it'd just be an empty module because we only want to share instance methods, but the whole thing feels pretty clunky.

Seems like the concern for sharing code is the easier approach still.