Record which controller action or job an error came from

[fractaledmind]

Fixes #37.

Since Rails 7.1, Rails puts the current controller or job into every error's context. The sanitizer stored any object as just its class, so occurrences showed "controller" => "#<UsersController>", and a record passed in context became "#<User>".

Now:

• Requests record controller: "UsersController#show" and params, taken from request.filtered_parameters, so the app's filter_parameters apply.
• Jobs record job (the class), job_id, queue and arguments. Arguments go through filter_parameters too.
• Records anywhere in the context are stored as their GlobalID (gid://app/User/1). Unsaved records keep the class-name form.

Context the app sets itself wins: params: or arguments: passed to Rails.error.set_context aren't overwritten. Job arguments are sanitized before filtering, so a proc in filter_parameters can't copy a record into an unsaved one and lose its GlobalID.

This needs no new settings and no patching of controllers or jobs, because Rails already supplies the objects. The README gains a short section on what an occurrence records. It also answers #44: job errors already reach Solid Errors through the Rails executor with Solid Queue, Sidekiq and GoodJob.

The tests use a real request and a real job in the dummy app, and check that params and arguments are filtered. Mutants that skip the filtering or the GlobalID conversion each fail a test.

🤖 Generated with Claude Code