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?
Damn it, I edited the post to clarify wording and the poll (and all the votes) disappeared.
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
Andy@bradwilson iMO, if it’s INFO most developers will ignore it until it breaks in v3. Many will still ignore it as a WARNING, but hopefully less.
Chet Husk@bradwilson warning in v2. users that run WarningsAsError will fix it immediately, and users that don't will at least have a work item in their IDE's errors/problems display.
Miha Markič@bradwilson For a moment I thought you're going against ex-Twitter ;-)
Lars Hanisch@bradwilson +1 for warning
Vincent Biret
MaxiTB@bradwilson Personally I would prefer a warning, because it aligns with the [Obsolete] attribute.