Skip to content

Allows linking nodes in the message flow view as a fallback when no link could be established on OriginatingEndpoint / ProcessingEndpoint mismatch #1294

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 6, 2022

Conversation

cquirosj
Copy link
Contributor

@cquirosj cquirosj commented Dec 6, 2022

Re-doing the changes from pull request #1171 into master

…ink could be established on OriginatingEndpoint / ProcessingEndpoint mismatch (#1171)

* Allows linking nodes if originating message is not an event in case there is no match on child.RelatedTo = parent.Id && child.OriginatingEndpoint = parent.ProcessingEndpoint

* Implemented logging TODO's

* Removed unneeded TODO

* Resolved ESSENTIAL formatting fix IDE0055......

* Apply suggestions from code review

Co-authored-by: Daniel Marbach <[email protected]>

* Update src/ServiceInsight/MessageFlow/MessageFlowViewModel.cs

* Using names instead of numbers for Serilog messages

* Fix missing ToArray

* Converted to switch for reabability of intent

Co-authored-by: Daniel Marbach <[email protected]>
# Conflicts:
#	src/ServiceInsight/MessageFlow/MessageFlowViewModel.cs
@cquirosj cquirosj requested review from HEskandari and soujay December 6, 2022 22:27
@soujay soujay merged commit cebb175 into master Dec 6, 2022
@soujay soujay deleted the endpoint-mismatch-fallback-cherry-pick branch December 6, 2022 22:36
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