You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CHANGELOG.md
+4
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,10 @@
2
2
3
3
Represents the **NuGet** versions.
4
4
5
+
## v3.10.0
6
+
-*Enhancement*: The `WebApiPublisher` publishing methods have been simplified (breaking change), primarily through the use of a new _argument_ that encapsulates the various related options. This will enable the addition of further options in the future without resulting in breaking changes or adding unneccessary complexities. The related [`README`](./src/CoreEx.AspNetCore/WebApis/README.md) has been updated to document.
7
+
-*Enhancement*: Added `ValidationUseJsonNames` to `SettingsBase` (defaults to `true`) to allow setting `ValidationArgs.DefaultUseJsonNames` to be configurable.
8
+
5
9
## v3.9.0
6
10
-*Enhancement*: A new `Abstractions.ServiceBusMessageActions` has been created to encapsulate either a `Microsoft.Azure.WebJobs.ServiceBus.ServiceBusMessageActions` (existing [_in-process_](https://learn.microsoft.com/en-us/azure/azure-functions/functions-dotnet-class-library) function support) or `Microsoft.Azure.Functions.Worker.ServiceBusMessageActions` (new [_isolated_](https://learn.microsoft.com/en-us/azure/azure-functions/dotnet-isolated-process-guide) function support) and used internally. Implicit conversion is enabled to simplify usage; existing projects will need to be recompiled. The latter capability does not support `RenewAsync` and as such this capability is no longer leveraged for consistency; review documented [`PeekLock`](https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-service-bus-trigger?tabs=python-v2%2Cisolated-process%2Cnodejs-v4%2Cextensionv5&pivots=programming-language-csharp#peeklock-behavior) behavior to get desired outcome.
7
11
-*Enhancement*: The `Result`, `Result<T>`, `PagingArgs` and `PagingResult` have had `IEquatable` added to enable equality comparisons.
[OpenApiResponseWithBody(statusCode:HttpStatusCode.Accepted,contentType:MediaTypeNames.Text.Plain,bodyType:typeof(string),Description="The OK response")]
Copy file name to clipboardexpand all lines: src/CoreEx.AspNetCore/Http/HttpResultExtensions.cs
+4-6
Original file line number
Diff line number
Diff line change
@@ -38,8 +38,7 @@ public static class HttpResultExtensions
38
38
/// <remarks>This will automatically invoke <see cref="ApplyETag(HttpRequest, string)"/> where there is an <see cref="HttpRequestOptions.ETag"/> value.</remarks>
Copy file name to clipboardexpand all lines: src/CoreEx.AspNetCore/README.md
+40-7
Original file line number
Diff line number
Diff line change
@@ -171,7 +171,7 @@ public class EmployeeFunction
171
171
172
172
## WebApiPublish
173
173
174
-
The [`WebApiPublisher`](./WebApis/WebApiPublisher.cs) classshouldbeleveragedforfire-and-forget style APIs, where the message is received, validated and then published as an event for out-of-process decoupled processing.
174
+
The [`WebApiPublisher`](./WebApis/WebApiPublisher.cs) classshouldbeleveragedfor_fire-and-forget_ style APIs, where the message is received, validated and then published as an event for out-of-process decoupled processing.
175
175
176
176
The `WebApiPublish` extends (inherits) [`WebApiBase`](./WebApis/WebApiBase.cs) thatprovidesthebase `RunAsync` methoddescribed [above](#WebApi).
177
177
@@ -181,12 +181,46 @@ The `WebApiPublisher` constructor takes an [`IEventPublisher`](../CoreEx/Events/
181
181
182
182
### Supported HTTP methods
183
183
184
-
A publish should be performed using an HTTP `POST` and as such this is the only HTTP method supported. The `WebApiPublish` provides the following overloads depending on need. Where a generic `Type` is specified, either `TValue` being the request content body and/or `TResult` being the response body, this signifies that `WebApi` will manage the underlying JSON serialization:
184
+
A publish should be performed using an HTTP `POST` and as such this is the only HTTP method supported. The `WebApiPublish` provides the following overloads depending on need.
/// An attribute that specifies the expected request <b>body</b> <see cref="Type"/> that the action/operation accepts and the supported request content types.
10
10
/// </summary>
11
11
/// <remarks>The is used to enable <i>Swagger/Swashbuckle</i> generated documentation where the operation does not explicitly define the body as a method parameter; i.e. via <see cref="Microsoft.AspNetCore.Mvc.FromBodyAttribute"/>.</remarks>
0 commit comments