Adding new Match option to Result object

Author: AlanBarber

.github/workflows/release-vscodetoolkit.yml

@@ -47,15 +47,6 @@ jobs:
         run: npx vsce package --out ResultR.VSCodeToolkit.${{ steps.version.outputs.VERSION }}.vsix
         working-directory: src/ResultR.VSCodeToolkit
 
-      - name: Publish to VS Code Marketplace
-        run: npx vsce publish --pat ${{ secrets.VSCODE_MARKETPLACE_TOKEN }}
-        working-directory: src/ResultR.VSCodeToolkit
-
-      - name: Publish to Open VSX Registry
-        run: npx ovsx publish ResultR.VSCodeToolkit.${{ steps.version.outputs.VERSION }}.vsix --pat ${{ secrets.OPEN_VSX_TOKEN }}
-        working-directory: src/ResultR.VSCodeToolkit
-        continue-on-error: true
-
       - name: Create GitHub Release
         uses: softprops/action-gh-release@v2
         with:

.github/workflows/release-vstoolkit.yml

@@ -57,13 +57,6 @@ jobs:
           }
         id: rename
 
-      - name: Publish to Visual Studio Marketplace
-        uses: CodingWithCalvin/GHA-VSMarketplacePublisher@v2.0.0
-        with:
-          marketplace-pat: ${{ secrets.VS_MARKETPLACE_TOKEN }}
-          publish-manifest-path: src/ResultR.VSToolkit/Resources/publishManifest.json
-          vsix-path: ${{ steps.rename.outputs.VSIX_PATH }}
-
       - name: Create GitHub Release
         uses: softprops/action-gh-release@v2
         with:

docs/wiki/The-Result-Type.md

@@ -167,6 +167,89 @@ public async Task<IActionResult> CreateUser(CreateUserRequest request)
 }
 ```
 
+### Pattern Matching with Match()
+
+The `Match()` method provides a functional approach to handling results by executing one of two callbacks based on success or failure:
+
+```csharp
+[HttpGet("{id}")]
+public async Task<IActionResult> GetUser(int id)
+{
+    var result = await _dispatcher.Dispatch(new GetUserRequest(id));
+    
+    return result.Match(
+        user => Ok(user),
+        error => NotFound(new { error })
+    );
+}
+
+[HttpPost]
+public async Task<IActionResult> CreateUser(CreateUserRequest request)
+{
+    var result = await _dispatcher.Dispatch(request);
+    
+    return result.Match(
+        user => CreatedAtAction(nameof(GetUser), new { id = user.Id }, user),
+        error => BadRequest(new { error })
+    );
+}
+```
+
+#### Accessing Exception Information
+
+Use the overload that accepts both error message and exception when you need detailed error information:
+
+```csharp
+[HttpGet("{id}")]
+public async Task<IActionResult> GetUser(int id)
+{
+    var result = await _dispatcher.Dispatch(new GetUserRequest(id));
+    
+    return result.Match(
+        user => Ok(user),
+        (error, exception) => 
+        {
+            if (exception is not null)
+            {
+                _logger.LogError(exception, "Failed to get user {UserId}", id);
+            }
+            return NotFound(new { error, hasException = exception is not null });
+        }
+    );
+}
+```
+
+#### Non-Generic Result
+
+The `Match()` method is also available on the non-generic `Result` type:
+
+```csharp
+public async Task<IActionResult> DeleteUser(int id)
+{
+    var result = await _dispatcher.Dispatch(new DeleteUserRequest(id));
+    
+    return result.Match(
+        () => NoContent(),
+        error => NotFound(new { error })
+    );
+}
+
+// With exception handling
+public async Task<IActionResult> DeleteUser(int id)
+{
+    var result = await _dispatcher.Dispatch(new DeleteUserRequest(id));
+    
+    return result.Match(
+        () => NoContent(),
+        (error, exception) => 
+        {
+            _logger.LogError(exception, "Failed to delete user {UserId}", id);
+            return StatusCode(500, new { error });
+        }
+    );
+}
+```
+
 ## Exception Handling
 
 ResultR automatically catches exceptions in handlers and converts them to failure results: