Closed kyanagi closed 7 years ago
It's not actually connected to Rake. In 0.6.2, within a Rails app, using ActiveType::Object
without first using ActiveRecord::Base
will produce this error. Working on a fix.
I've just released 0.6.3, which should fix this issue. Thanks for reporting!
This problem is reproduced with active_type 0.6.2, not with 0.6.1.