Why is TestContextBase now a mandatory parameter to FakeNavigationManager?

[vedion]

Hi,

In the latest version it was changed so the FakeNavigationManager constructor takes a TestContextBase:

public FakeNavigationManager(TestContextBase testContextBase)
{
	this.testContextBase = testContextBase;
	Initialize("http://localhost/", "http://localhost/");
}

The TestContextBase is IDisposable and that complicates my existing tests if I have to new and dispose a TestContextBase.
All my tests works fine if I just force TextContextBase to null:
Fixture.Inject<NavigationManager>(new FakeNavigationManager(null!));

Would it make sense to consider an empty constructor for FakeNavigationManager?

Best Regards,
Anders Havn

[egil]

It was done to support the "supply parameter from query" feature and the changes that came with that in .NET 8.

Are you using the FakeNavigationManager in a context outside of bUnit directly? The purpose for passing in a TestContext is that it provides access to the renderer which in turn provides access to the Dispatcher, which we need to use when triggering a navigation on a rendered component.

[vedion]

We have services that inject the NavigationManager. The service doesn't render anything so we use FakeNavigationManager in a context outside of bUnit directly. It is fair that it is not a supported case and we will just use:
new FakeNavigationManager(null!)