Don't use conflicting module names - messes up 'included' blocks, etc

laserlemon / vestal_versions

Keep a DRY history of your ActiveRecord models' changes

MIT License

933 stars 229 forks source link

Open pdf opened 11 years ago

pdf commented 11 years ago

This isn't evident with ClassMethods, but only because ActiveRecord::Concern does some magic...

pelargir commented 9 years ago

+1 for pulling this in. Fixes a problem I ran into when upgrading to Rails 4.