Skip to content

Use generated saga correlation accessors and emit finder-only sagas - #7924

Merged
danielmarbach merged 1 commit into
release-10.2from
metadata
Sep 3, 2026
Merged

Use generated saga correlation accessors and emit finder-only sagas#7924
danielmarbach merged 1 commit into
release-10.2from
metadata

Conversation

@danielmarbach

Copy link
Copy Markdown
Contributor

Partial backport of cd2db0b (#7918) to release-10.2, complementing the #7922 generator fix.

SagaMetadata.Create now forwards the generated correlation accessor to SagaMapper, so correlation ids load through the source-generated accessor instead of runtime expression compilation. The saga source generator parses and emits finder-only sagas with a null correlation accessor, and the AddSaga IL2026 suppressor only suppresses when an interceptor can actually be emitted.

The AddMessage<>-related changes of the original commit are intentionally not backported.

Partial backport of cd2db0b (#7918) to release-10.2, complementing the #7922 generator fix.

SagaMetadata.Create now forwards the generated correlation accessor to SagaMapper, so correlation ids load through the source-generated accessor instead of runtime expression compilation. The saga source generator parses and emits finder-only sagas with a null correlation accessor, and the AddSaga IL2026 suppressor only suppresses when an interceptor can actually be emitted.

The AddMessage<>-related changes of the original commit are intentionally not backported.
@danielmarbach
danielmarbach merged commit 202dfdf into release-10.2 Sep 3, 2026
4 checks passed
@danielmarbach
danielmarbach deleted the metadata branch September 3, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants