Open joelvh opened 8 years ago
@pencil any reason this was not pulled in?
@pencil can this be merged in?
@pencil any interest in pulling this in? I think it's very reasonable not to have to be forced to use CASino::User
namespace - unless there is another approach to this already in the gem?
Create a configurable way to specify a superclass for
CASino::User
. This allows CASino to become an extension of an existing application, where the "user" is the joining model for many other relationships. This is a clean way to make sure the "user" association on other CASino models are of the proper user class as well.