Merge branch 'main' into main

Author: egil

.github/ISSUE_TEMPLATE/bug_report.md

@@ -4,13 +4,14 @@ about: Create a report to help us improve
 title: ''
 labels: ''
 assignees: ''
-
 ---
 
-**NOTE:** _Remove any parts of the template you do not need and replace the default text in each section with your own, including this._
+<!-- **NOTE:** Remove any parts of the template you do not need and
+replace the default text in each section with your own, including this. -->
+
+**Describe the bug**
 
-**Describe the bug or question**
-_A clear and concise description of what the bug or question is._
+<!-- A clear and concise description of the bug. This include a list of reproduction steps. -->
 
 **Example:**
 Testing this component:
@@ -32,11 +33,15 @@ Message output from running the test.
 ```
 
 **Expected behavior:**
-A clear and concise description of what you expected to happen.
+
+<!-- A clear and concise description of what you expected to happen. -->
 
 **Version info:**
- - Library version: 
- - .NET Core/Blazor version:
+
+ - bUnit version: 
+ - .NET Runtime and Blazor version:
+ - OS type and version:
 
 **Additional context:**
-Add any other context about the problem here.
+
+<!-- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,22 +1,26 @@
 ---
 name: Feature request
-about: Suggest an idea for this project
+about: Suggest an idea or enhancement for this project
 title: ''
 labels: ''
 assignees: ''
 
 ---
 
-**NOTE:** _Remove any parts of the template you do not need and replace the default text in each section with your own, including this._
+<!-- NOTE: Remove any parts of the template not needed and fill in as needed. -->
 
-**Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+**Is the feature request related to a problem? Please elaborate.**
 
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
+<!-- A clear and concise description of what the problem is. -->
 
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
+**The suggested solution**
+
+<!-- A clear and concise description of the suggested solution. -->
+
+**Describe any alternative solutions**
+
+<!-- A clear and concise description of any alternative solutions or features considered. -->
 
 **Additional context**
-Add any other context or screenshots about the feature request here.
+
+<!-- Add any other context or screenshots about the feature request here. -->

docs/site/docs/test-doubles/emulating-ijsruntime.md

@@ -7,7 +7,7 @@ title: Emulating Blazor's IJSRuntime
 
 It is common for Blazor components to use `IJSRuntime` to call JavaScript, and since bUnit does not run JavaScript, emulating `IJSRuntime` is needed for components that use it. In that regard, `IJSRuntime` is no different than other services that a component might depend on.
 
-bUnit comes with it's own JSInterop, a tailor-made implementation of `IJSRuntime` that is _active by default_, allowing you to specify how JavaScript interop calls should be handled and what values the calls should return, and also allowing you to verify that they the calls have happened. The implementation runs in "strict mode", which means means it will throw an exception if it receives an invocation it has not been configured to handle. See more about strict vs. loose mode in the following section.
+bUnit comes with it's own JSInterop, a tailor-made implementation of `IJSRuntime` that is _active by default_, allowing you to specify how JavaScript interop calls should be handled and what values the calls should return, and also allowing you to verify that they the calls have happened. The implementation runs in "strict mode", which means it will throw an exception if it receives an invocation it has not been configured to handle. See more about strict vs. loose mode in the following section.
 
 If you prefer to use the same mocking framework for all mocking in your tests to keep things consistent, general-purpose mocking frameworks like [Moq](https://github.com/Moq), [JustMock Lite](https://github.com/telerik/JustMockLite), or [NSubstitute](https://nsubstitute.github.io/) all work nicely with bUnit and can be used to mock `IJSRuntime`. In general, registering an implementation of `IJSRuntime` with bUnit's `Services` collection replaces bUnit's implementation.
 
@@ -27,7 +27,7 @@ By default, the bUnit's JSInterop runs in **Strict** mode. To change the mode, d
 
 ```csharp
 using var ctx = new TestContext();
-ctx.JSInterop.Mode = JSRuntimeMockMode.Loose;
+ctx.JSInterop.Mode = JSRuntimeMode.Loose;
 ```
 
 ## Setting up invocations
@@ -58,8 +58,8 @@ var plannedInvocation = ctx.JSInterop.SetupVoid("startAnimation");
 // only completes or throws, it doesn’t return a value.
 // Any calls to InvokeVoidAsync(...) up till this point will
 // have received an incomplete Task which the component 
-// is awaiting until the call to SetCompleted() below.
-plannedInvocation.SetCompleted();
+// is awaiting until the call to SetVoidResult() below.
+plannedInvocation.SetVoidResult();
 ```
 
 ## Verifying invocations
@@ -99,7 +99,7 @@ By default, a module Interop inherits the `Mode` setting from the root JSInterop
 
 ```csharp
 var moduleInterop = ctx.JSInterop.SetupModule("hello.js");
-moduleInterop.Mode = JSRuntimeMockMode.Loose;
+moduleInterop.Mode = JSRuntimeMode.Loose;
 ```
 
 ### Support for `IJSInProcessObjectReference` and `IJSUnmarshalledObjectReference`
@@ -156,4 +156,4 @@ ctx.JSInterop.VerifyFocusAsyncInvoke() // Verifies that a FocusAsync call has ha
 
 bUnit's `IJSRuntime` supports being cast to the `IJSInProcessRuntime` and `IJSUnmarshalledRuntime` types, just like Blazor's `IJSRuntime`. 
 
-To set up a handler for `Invoke` and `InvokeUnmarshalled` calls, just use the regular `Setup` and `SetupVoid` methods on bUnit's JSInterop.
+To set up a handler for `Invoke` and `InvokeUnmarshalled` calls, just use the regular `Setup` and `SetupVoid` methods on bUnit's JSInterop.