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
As a library, unless you explicitly need to capture context, every await call should be followed by a ConfigureAwait(false).
Reason being, as a library author, you don't know how this is going to be consumed. For example, in our case, we are throwing the context away earlier on in the process by using .ConfigureAwait(false), prior to calling this library. In turn, this causes a deadlock when we call the async methods in this library, and tasks never complete. This effectively means that we can't use the asynchronous library calls 🤷♂️
The text was updated successfully, but these errors were encountered:
As a library, unless you explicitly need to capture context, every
await
call should be followed by aConfigureAwait(false)
.Reason being, as a library author, you don't know how this is going to be consumed. For example, in our case, we are throwing the context away earlier on in the process by using
.ConfigureAwait(false)
, prior to calling this library. In turn, this causes a deadlock when we call the async methods in this library, and tasks never complete. This effectively means that we can't use the asynchronous library calls 🤷♂️The text was updated successfully, but these errors were encountered: