Steven Weerdenburg

A recent pull request (#4307 ) for a bugfix caused me to think back to this issue. @nunit/framework-team @nunit/core-team @oznetmaster Is there interest in this issue proceeding or should it...

I also don't feel strongly one way or another about the behavior here, and I'd probably want to experiment a bit at a computer before forming an opinion. If we...

@maettu-this Sorry, but I'm starting to lean towards @mikkelbu suggestion as well based on a bit of experimentation with other APIs which people may be used to and expect similar...

I've transferred this to the documenation repo since it sounds like we want to keep the behaviour the same as it is today

@SeanKilleen Curious, how would something like this be approached for unreleased changes? Is there a "prerelease" section of the docs, or should a PR be put up and just not...

Thanks @OsirisTerje @SeanKilleen ! I'll give that a try.

Spare time has been a bit hard to come by lately. I'm going to remove my assignment from this for now in case anyone else wishes to pick this up

@mariusz96 The Nunit analyzers are currently shipped in a separate package, [nunit.analyzers](https://www.nuget.org/packages/NUnit.Analyzers). I think rule `NUnit1030` may cover what you're looking for: https://docs.nunit.org/articles/nunit-analyzers/NUnit1030.html Can you see if that works for...

Glad it helped @mariusz96 ! And thank you for the question. It's likely an area which could be improved, but would likely require changes coordinated between the framework and the...

@OsirisTerje The new namespace is a good point. This appears to be the first time we're explicitly adding a new writer with external intent. Current writers are all in the...