Work with models other than User about ahoy_email HOT 5 CLOSED

He doesn't want to pick a particular user, he wants to use a different model completely. He is not tracking users, he is tracking subscribers. I too have a Subscriber model that I wish to track. As mentioned before, mailkick handles this perfectly but I cannot seem to do it with this gem.

from ahoy_email.

@ollieglass user is polymorphic, so it already supports any user model. https://github.com/ankane/ahoy_email/blob/master/app/models/ahoy/message.rb#L5

from ahoy_email.

I see... so I say my model (Subscriber) has_many :messages, as: :user... and that won't conflict with another model called User?

Won't this line require the model to be called User?

Sorry if I'm not getting it!

from ahoy_email.

@ollieglass that shouldn't be an issue, although the naming of this polymorphic relationship is rather awkward. And yes, your semantics are correct there. Although I'd worry about using this on a Subscriber class when you also have a User class. Things could get awkward pretty quickly.

You wonder if something like: belongs_to :messageable, polymorphic: true wouldn't be better, in which case you could include a global override to specify the model of your choice.

I just think it's weird to technically have a User class that also has a "User" for its user_type. :)

from ahoy_email.

@ollieglass that's the default user option, but you can pass whatever you'd like to track user: any_user.

from ahoy_email.