-
Notifications
You must be signed in to change notification settings - Fork 197
General merit workflow
This is an explanation of how does merit process reputation starting from an HTTP request made to an endpoint with associated rules[1]. It's meant for merit developers, not directly helpful for application set up.
-
Merit sets an application-wide
after_filter
, which creates amerit_action
for the request if that controller/action pair has associated rules. -
Controller
after_filter
tellsMeritAction
class to process it's unprocessed activity (will typically be the newly createdmerit_action
). It can be done synchronously (default) or as a background job. -
merit_action
asks ajudge
to grant reputation, given the sash and rule in question. -
The
judge
will grant or remove badges and points from it's sash according to therule
[1].
[1] Reputation rules are set in the application via the DSL defined in files rules_{badge|points|rank}_methods.rb