Register a known side effect #29
Description
It'd be neat to identify a method you associate with a side effect (like an http.post) and then wrap it. Still calling through but warning the user?
As for default registrations, I suspect vcr or webmock might have some prior art on this from an HTTP perspective? Would be good to have an API that could handle database/socket connections as well.