馃攰 Warn about deprecated #responses usage
#97
Conversation
|
@shugo Because #93 is such a big change to existing usage, I split the deprecation warnings into a separate PR. I'd like to take a look at the top reverse dependencies and submit forward-compatible PRs to them, before we start flooding their logs with new warnings! |
nevans
force-pushed
the
response-handlers
branch
from
51f57de
to
8e63a33
Compare
|
FYI, |
Thanks. I had forgotten about that. If I remember correctly, I did try to use |
Yes, you're right. I forgot that |
nevans
force-pushed
the
response-handlers
branch
from
8e63a33
to
40a15db
Compare
nevans
force-pushed
the
response-handlers
branch
2 times, most recently
from
857dabb
to
bbaa32a
Compare
nevans
force-pushed
the
response-handlers
branch
2 times, most recently
from
d800e82
to
c58afb8
Compare
nevans
force-pushed
the
response-handlers
branch
from
c58afb8
to
6cb82ff
Compare
nevans
force-pushed
the
response-handlers
branch
2 times, most recently
from
c835ad5
to
ecba223
Compare
nevans
force-pushed
the
response-handlers
branch
from
ecba223
to
0ccd250
Compare
This was extracted from #93 and split into a separate PR. This allows us to prepare dependent projects for the new behavior before their logs are flooded with deprecation warnings.
This is provided as a temporary workaround, until dependant projects can update their usage. A future release will remove this backwards compatibility, but no sooner than one year after the release that contains this deprecation warning.
This was extracted from #93 and split into a separate PR.
This allows us to prepare dependent projects for the new behavior before their logs are flooded with deprecation warnings.
Also adds
Net::IMAP.attr_accessor :silence_thread_safety_deprecation_warnings. This is provided as a temporary workaround, until dependant projects can update their usage.