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: src/content/docs/release-notes/mediator.mdx
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,7 @@ import RN from '/src/components/ReleaseNote.astro';
9
9
<RNtype="feature"breaking={true}>Moving to .NET 8 & 10 as minimum target</RN>
10
10
<RNtype="feature"breaking={true}>New HTTP Client Source Generation now generates handlers, contracts, JSON converters, and registration to make it fully compatible. This will require you to call a new registration method, but its setup through MediatorHttpItem remains the same</RN>
11
11
<RNtype="feature"breaking={true}>DirectHttpRequest is gone. You can create your own HTTP objects as before which will source generate a handler</RN>
12
+
<RNtype="enhancement">New PublishToBackground on IMediator and IMediatorContext intended to fix scoping issues that can occur on aspnet fire & forget scenarios. This new method spawns a new child scope so you can continue to run without worrying about disposal. Note that you can still use Publish to await all event completions using the same service scope</RN>
12
13
<RNtype="enhancement">The HTTP Client source generation no longer ignores missing OperationIDs. It inferes the contact name using the HTTP verb and path info (ie. GET /user/list = GetUserList)</RN>
13
14
<RNtype="enhancement">ASPNET no longer enforces operation ID in the attribute setup</RN>
14
15
<RNtype="enhancement">We now support async enumerable responses. Sample below:</RN>
0 commit comments