C#•2y ago

❔ ✅ Rider is out of its mind about `async` code

I updated Rider and now it wants me to return tasks straight instead of awaiting them, as in

async Task<int> BarAsync() => ...;
async Task<int> FooAsync() => BarAsync();

async Task<int> BarAsync() => ...;
async Task<int> FooAsync() => BarAsync();

instead of

async Task<int> BarAsync() => ...;
async Task<int> FooAsync() => await BarAsync();

async Task<int> BarAsync() => ...;
async Task<int> FooAsync() => await BarAsync();

and wants me to use .ConfigureAwait() literally everywhere The first one is a bad practice since it leads to bad stack traces, and the second one is arguable at best, bad practice at worst. What changed?

6 Replies

AngiusOP•2y ago

Or maybe I'm tripping balls and Rider is actually right and gives me good advice

AngiusOP•2y ago

Rider, wtf, who hurt you baby...?

AngiusOP•2y ago

Turns out it was a plugin named Async Converter

arion•2y ago

Some rider plugins are bad, but sometimes u get rare jewels. I remember seeing some plugins that alert the user when their reflection is likely to fail, or when you write code that results in a closure

ero•2y ago

With that spelling and grammar I would not have thought that that's a native Rider feature

Accord•2y ago

Was this issue resolved? If so, run /close - otherwise I will mark this as stale and this post will be archived until there is new activity.

Gaming

Programming

❔ ✅ Rider is out of its mind about `async` code