You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is it possible or could be added the capability of displaying the exposed aggregates in the relationship between 2 bounded context like it's currently being done with the "implementationTechnology" pattern?
I know this is done when generating the PlantUML diagram of the context map, but I was wondering if it was possible to display it on the one generated by the Context Map Generator. This diagram is much simpler and easier to visualize than the PlantUML one and would be a great addition to display this as well.
Thanks!
The text was updated successfully, but these errors were encountered:
Thanks for reporting your idea @CesarD! I'll have to check how to visualize it (especially if there are many exposed aggregates), but I like the idea. Could be something for a next release... Thanks.
In the line of what you said, about figuring how to visualize it if there are too many things to display (and perhaps this is worth another issue), but is there any way to flag what attributes to display or hide? ie. perhaps I want to document in the CML the implementationTechnology but I don't care to display it in the generated diagram... Perhaps same could be applied for the exposed aggregates... But if there's no way right now for that, it could be an entire new feature.
Is it possible or could be added the capability of displaying the exposed aggregates in the relationship between 2 bounded context like it's currently being done with the "implementationTechnology" pattern?
I know this is done when generating the PlantUML diagram of the context map, but I was wondering if it was possible to display it on the one generated by the Context Map Generator. This diagram is much simpler and easier to visualize than the PlantUML one and would be a great addition to display this as well.
Thanks!
The text was updated successfully, but these errors were encountered: