Merge pull request #35410 from dotnet/main

Author: guardrex

aspnetcore/blazor/security/webassembly/additional-scenarios.md

@@ -300,6 +300,15 @@ public class CustomAuthorizationMessageHandler : AuthorizationMessageHandler
 }
 ```
 
+> [!NOTE]
+> In this section, the preceding message handler is used when a configured <xref:System.Net.Http.HttpClient> is created from an injected <xref:System.Net.Http.IHttpClientFactory>. If you don't use an <xref:System.Net.Http.IHttpClientFactory>, you must create an <xref:System.Net.Http.HttpClientHandler> instance and assign it to the <xref:Microsoft.AspNetCore.Components.WebAssembly.Authentication.AuthorizationMessageHandler>'s <xref:System.Net.Http.DelegatingHandler.InnerHandler%2A?displayProperty=nameWithType>:
+>
+> ```csharp
+> InnerHandler = new HttpClientHandler();
+> ```
+>
+> You don't need to make the preceding <xref:System.Net.Http.DelegatingHandler.InnerHandler> assignment if you use <xref:System.Net.Http.IHttpClientFactory>, as the `ExampleAPIMethod` call later in this section demonstrates.
+
 In the preceding code, the scopes `example.read` and `example.write` are generic examples not meant to reflect valid scopes for any particular provider.
 
 In the `Program` file, `CustomAuthorizationMessageHandler` is registered as a transient service and is configured as the <xref:System.Net.Http.DelegatingHandler> for outgoing <xref:System.Net.Http.HttpResponseMessage> instances made by a named <xref:System.Net.Http.HttpClient>.
@@ -378,7 +387,10 @@ builder.Services.AddScoped(sp => new HttpClient(
 });
 ```
 
-In the preceding code, the scopes `example.read` and `example.write` are generic examples not meant to reflect valid scopes for any particular provider.
+In the preceding code:
+
+* The scopes `example.read` and `example.write` are generic examples not meant to reflect valid scopes for any particular provider.
+* <xref:System.Net.Http.IHttpClientFactory> isn't used to create <xref:System.Net.Http.HttpClient> instances, so an <xref:System.Net.Http.HttpClientHandler> instance is manually created and assigned to the <xref:Microsoft.AspNetCore.Components.WebAssembly.Authentication.AuthorizationMessageHandler>'s <xref:System.Net.Http.DelegatingHandler.InnerHandler%2A?displayProperty=nameWithType>.
 
 :::moniker range="< aspnetcore-8.0"
 

aspnetcore/fundamentals/openapi/overview.md

@@ -1,8 +1,8 @@
 ---
 title: Overview of OpenAPI support in ASP.NET Core API apps
-author: wadepickett
+author: rick-anderson
 description: Learn about OpenAPI features in ASP.NET Core.
-ms.author: wpickett
+ms.author: riande
 monikerRange: '>= aspnetcore-6.0'
 ms.date: 8/02/2024
 uid: fundamentals/openapi/overview

aspnetcore/performance/rate-limit-samples.md

@@ -1,5 +1,5 @@
 ---
-title: Rate limiting middleware samsples
+title: Rate limiting middleware samples
 author: rick-anderson
 ms.author: riande
 monikerRange: '>= aspnetcore-7.0'

aspnetcore/release-notes/aspnetcore-10/includes/OpenApiSchemasInTransformers.md

@@ -0,0 +1,42 @@
+### Support for generating OpenApiSchemas in transformers
+<!-- https://github.com/dotnet/aspnetcore/pull/61050 -->
+
+Developers can now generate a schema for a C# type, using the same logic as ASP.NET Core OpenAPI document generation,
+and add it to the OpenAPI document. The schema can then be referenced from elsewhere in the OpenAPI document.
+
+The context passed to document, operation, and schema transformers now has a `GetOrCreateSchemaAsync` method that can be used to generate a schema for a type.
+This method also has an optional `ApiParameterDescription` parameter to specify additional metadata for the generated schema.
+
+To support adding the schema to the OpenAPI document, a `Document` property has been added to the Operation and Schema transformer contexts. This allows any transformer to add a schema to the OpenAPI document using the document's `AddComponent` method.
+
+#### Example
+
+To use this feature in an document, operation, or schema transformer, create the schema using the `GetOrCreateSchemaAsync` method provided in the context
+and add it to the OpenAPI document using the document's `AddComponent` method.
+
+<!-- In the docs, highlight the lines with the call to "GetOrCreateSchemaAsync" and "AddComponent" -->
+```csharp
+builder.Services.AddOpenApi(options =>
+{
+    options.AddOperationTransformer(async (operation, context, cancellationToken) =>
+    {
+        // Generate schema for error responses
+        var errorSchema = await context.GetOrCreateSchemaAsync(typeof(ProblemDetails), null, cancellationToken);
+        context.Document?.AddComponent("Error", errorSchema);
+
+        operation.Responses ??= new OpenApiResponses();
+        // Add a "4XX" response to the operation with the newly created schema
+        operation.Responses["4XX"] = new OpenApiResponse
+        {
+            Description = "Bad Request",
+            Content = new Dictionary<string, OpenApiMediaType>
+            {
+                ["application/problem+json"] = new OpenApiMediaType
+                {
+                    Schema = new OpenApiSchemaReference("Error", context.Document)
+                }
+            }
+        };
+    });
+});
+```