Skip to content
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

Context Map does not work when a service is in multiple domains #1095

Open
otbe opened this issue Jan 13, 2025 · 1 comment
Open

Context Map does not work when a service is in multiple domains #1095

otbe opened this issue Jan 13, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@otbe
Copy link
Contributor

otbe commented Jan 13, 2025

I tried this:

Mainly for legacy reasons we have services that are part of multiple domains (= emitting events from this domain).

Currently I think the context map shows each service only once (last occasion) because of this line: https://github.com/event-catalog/eventcatalog/blob/main/eventcatalog/src/utils/node-graphs/domains-node-graph.ts#L118

Theres an unused "serviceNodeId" variable above which would it make work.

This happened:

The service is only shown once.

I expected this:

Actually I would expect that we can have the same service in multiple domains and that the edges are added between domains on an event level. That means even if someone consumes events emitted by a certain service there aren't two edges if the service is part of 2 domains.

Is there a workaround?

No response

Anything else?

No response

EventCatalog Version

2.19.1

Node.js Version

22

Platform(s)

Linux

Community Notes

  • Please vote by adding a 👍 reaction to the issue to help us prioritize.
  • If you are interested to work on this issue, please leave a comment.
@otbe otbe added the bug Something isn't working label Jan 13, 2025
@boyney123
Copy link
Collaborator

Thanks for raising @otbe , the context map feature is still very new, and when we come to look at these bugs and next version of it (making it better) we will take these issues/bugs into account, thanks for sharing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants