38d56542eb
* Add audit logging for negative reactions This change saves requests that create negative reactions to the audit log. We need to be monitoring admin and moderator actions throughout the app to increase visiblity on how our tools are being used and identify abuse. Additionally, this will help east concerns about giving elevated users more powerful tools. * Add a basic UI for moderator audit logs * Log experience level ratings * Log tag adjustments * UI tweaks for moderator actions log * Add logging to internal reactions controller * Add logging for admin actions on users and articles * Add searching to the moderator actions table * Move audit instrumentation out of concern We are able to use a PORO here instead of using a Rails concern. Moving this also makes syntax to audit something quite a bit more explicit and obvious to future developers * Change moderator logs pagination page length * Move auditing to after action filters * Add moderator actions to the internal navbar * Add request spec for internal moderator actions * Use request params to populate AuditLog slug
7 lines
282 B
Ruby
7 lines
282 B
Ruby
class ModeratorAction < ApplicationRecord
|
|
resourcify
|
|
# This class exists to take advantage of Rolify for limiting authorization
|
|
# on internal reports.
|
|
# NOTE: It is not backed by a database table and should not be expected to
|
|
# function like a traditional Rails model
|
|
end
|