You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At current, responsibility_id gets assigned by wrapping any command with a block, which works great in situations like controllers or operations that can be dealt with in lifecycles, but this makes wrapping an entire console session in production a bit more cumbersome.
While I'm open to suggestions on how best to wrap console with the Logidze.with_responsible block, that would require a bit more hacking than feels appropraite.
Is there another sane way to add default or fallback responsibility_id tracking for all actions that might happen in a rails console session?
The text was updated successfully, but these errors were encountered:
Feature Request
At current, responsibility_id gets assigned by wrapping any command with a block, which works great in situations like controllers or operations that can be dealt with in lifecycles, but this makes wrapping an entire console session in production a bit more cumbersome.
While I'm open to suggestions on how best to wrap console with the
Logidze.with_responsible
block, that would require a bit more hacking than feels appropraite.Is there another sane way to add default or fallback responsibility_id tracking for all actions that might happen in a rails console session?
The text was updated successfully, but these errors were encountered: