Skip to content

Conversation

@DavidBoike
Copy link
Member

@DavidBoike DavidBoike commented Jan 7, 2026

Also adds a test to ensure that a saga not found handler will not trigger a diagnostic, as it is a new API on SagaMapper. There was already a test added for custom saga finders.

Copy link
Contributor

@danielmarbach danielmarbach left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm good with it. I would vote though to adjust NSB0004 message because multiple is not relevant. The code must be rewritten regardless. Thoughts?

The saga mapping contains multiple .ToSaga(…) expressions which must be rewritten using mapper.MapSaga(…).ToMessage(…) syntax. Use the code fix to transition to the new syntax.

Pre approving

@DavidBoike DavidBoike merged commit e0aa9af into copilot/update-saga-diagnostics-error Jan 7, 2026
4 checks passed
@DavidBoike DavidBoike deleted the merge-diagnostics branch January 7, 2026 22:48
DavidBoike added a commit that referenced this pull request Jan 7, 2026
…7576)

* Initial plan

* Change NSB0018 saga diagnostic from Info to Error

Co-authored-by: danielmarbach <174258+danielmarbach@users.noreply.github.com>

* Change NSB0004 saga diagnostic from Warning to Error

Co-authored-by: danielmarbach <174258+danielmarbach@users.noreply.github.com>

* Merge saga diagnostics now that they're both error (#7579)

* Merge diagnostics

* Adjust message

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: danielmarbach <174258+danielmarbach@users.noreply.github.com>
Co-authored-by: David Boike <david.boike@gmail.com>
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.

3 participants