4 Commits

Author	SHA1	Message	Date
Jan Provaznik	0fc9f9d3e7	Add version 4.2 to all existing migrations ... DB schema generated by a migration may look different in rails 4 and 5 (because rails 5 may use different default values). For this reason it's important to explicitly set for which rails version a migration was written for. See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912	2018-11-22 13:18:28 +01:00
Sean McGivern	1ab33b15d1	Add cop for use of remove_column ... remove_column should only be used in the up (or change) step of a migration if it's a post-deployment migration. Otherwise there will be downtime due to the ActiveRecord column cache, which we can avoid by using the IgnorableColumn concern in combination with a post-deployment migration.	2017-12-11 16:34:51 +00:00
Patricio Cano	43e756d4ea	Refactored AkismetHelper into AkismetService and cleaned up `Spammable` ... - Refactored SpamCheckService into SpamService	2016-08-15 13:18:15 -05:00
Patricio Cano	64ab2b3d9f	Refactored spam related code even further ... - Removed unnecessary column from `SpamLog` - Moved creation of SpamLogs out of its own service and into SpamCheckService - Simplified code in SpamCheckService. - Moved move spam related code into Spammable concern	2016-08-15 13:18:15 -05:00