Summary of PR #7510: Obsolete old saga mapping API #7511
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a summary of the changes in #7510, which obsoletes the old saga mapping API in favor of the
MapSaga()fluent syntax.Breaking Change
The old
ConfigureMapping<T>().ToSaga()pattern is now a compile-time error. UseMapSaga().ToMessage<T>()instead.Before:
After:
Changes
error: true):ConfigureMapping<T>(),ConfigureHeaderMapping<T>(),IToSagaExpression<T>,ToSagaExpression<T,M>RewriteConfigureHowToFindSagaFixer.cs,NSB0018diagnostic, old syntax parsing inSagaAnalyzerToSagaExpression.cs,IToSagaExpression.cs,MessageHeaderToSagaExpression.csStats
+370/-1,862 lines across 52 files. Labeled as breaking change, targeted at vNext milestone.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.