- 06 Jul, 2017 1 commit
-
-
Yorick Peterse authored
This is allowed for existing instances so we don't end up 76 offenses right away, but for new code one should _only_ use this if they _have_ to remove non database data. Even then it's usually better to do this in a service class as this gives you more control over how to remove the data (e.g. in bulk).
-
- 21 Mar, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 21 Feb, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 20 Feb, 2017 1 commit
-
-
Z.J. van de Weg authored
-
- 07 Feb, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 02 Feb, 2017 1 commit
-
-
Sean McGivern authored
Apply the same spam checks to public snippets (either personal snippets that are public, or public snippets on public projects) as to issues on public projects.
-
- 23 Aug, 2016 1 commit
-
-
Patricio Cano authored
-
- 15 Aug, 2016 5 commits
-
-
Patricio Cano authored
-
Patricio Cano authored
- Refactored SpamCheckService into SpamService
-
Patricio Cano authored
- Added controller actions as reusable concerns - Added controller tests
-
Patricio Cano authored
- 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
-
Patricio Cano authored
- Merged `AkismetSubmittable` into `Spammable` - Clean up `SpamCheckService` - Added tests for `Spammable` - Added submit (ham or spam) options to `AkismetHelper`
-
- 27 Jul, 2016 1 commit
-
-
Patricio Cano authored
Refactor spam validation to a concern that can be easily reused and improve legibility in `SpamCheckService`
-