Better error message from JSInterop when detecting an unconfigured module import

[egil]

The suggestion produced in the exception message for an unconfigured import of a module in JSInterop is not correct.

bUnit's JSInterop has not been configured to handle the call:

    InvokeAsync<IJSObjectReference>("import", "./_content/BlazorPro.BlazorSize/blazorSizeMediaModule.js")

Configure bUnit's JSInterop to handle the call with following:

    Setup<IJSObjectReference>("import", "./_content/BlazorPro.BlazorSize/blazorSizeMediaModule.js")
or the following, to match any arguments:
    Setup<IJSObjectReference>("import", _ => true)

The setup methods are available on an instance of the BunitJSInterop or
BunitJSModuleInterop type. The standard BunitJSInterop is available
through the TestContext.JSInterop property, and a BunitJSModuleInterop
instance is returned from calling SetupModule on a BunitJSInterop instance.

should be:

bUnit's JSInterop has not been configured to handle the call:

    InvokeAsync<IJSObjectReference>("import", "./_content/BlazorPro.BlazorSize/blazorSizeMediaModule.js")

Configure bUnit's JSInterop to handle the call with following:

    SetupModule("./_content/BlazorPro.BlazorSize/blazorSizeMediaModule.js")

The setup methods are available on an instance of the BunitJSInterop or
BunitJSModuleInterop type. The standard BunitJSInterop is available
through the TestContext.JSInterop property, and a BunitJSModuleInterop
instance is returned from calling SetupModule on a BunitJSInterop instance.

[jgoday]

@egil would it be enough to check that 'import' is being called in JSRuntimeUnhandledInvocationException.CreateErrorMessage? (and then personalize the error message)

[egil]

@jgoday I think you can look in the Setup methods for a stable way to detect if its an attempt to set up a module import. Something similar can be used in exception.

I have not had time to look into how I would design it myself though, so do submit a proposal before you get too far into coding a solution.

[jgoday]

@jgoday I think you can look in the Setup methods for a stable way to detect if its an attempt to set up a module import. Something similar can be used in exception.

I have not had time to look into how I would design it myself though, so do submit a proposal before you get too far into coding a solution.

Created a PR #425 then.