Brad WilsonIf I'm writing an analyzer to say "stop doing X in xUnit.net v2 because it's been removed in v3", should that be INFO or WARNING by default?
Robert "Anaerin" Johnston@bradwilson It should be an INFO in v2, and upgraded to a WARNING in v3, followed by the inevitable ERROR in v4 when it's been removed.
@anaerin No, it’s actually removed in v3, so ERROR is correct there.
xUnit.net (@[email protected])
We are removing `async void` test support in v3. Tests marked that way will fast fail with a message telling you to change to `Task` or `ValueTask`. We originally added `async void` support long before the days of IDEs helping them with auto-converting methods to be async. The most common gesture we saw was taking a `void` test and just adding `async` in front of it, so we made it work. 🤷♂️ #dotnet #csharp #unittest
Dan Kearney@bradwilson @anaerin then it should be a Warning in the immediately preceding version