We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
An aggregate might be present in multiple bounded contexts, in different forms. For example, as described in https://docs.microsoft.com/en-us/dotnet/architecture/microservices/architect-microservice-container-applications/identify-microservice-domain-model-boundaries (Figure 4-10), a User from one bounded context can be a Buyer in another. Could this be expressed somehow in terms of the DSL or the generators? Ideally the outcome would be something like this:
User
Buyer
The text was updated successfully, but these errors were encountered:
Hi @milanov
Thanks for creating the issue and very sorry for the late response!
I love the idea to visualize that; but unfortunately we don't have that feature yet. Of course we are always happy to receive PRs ;)
I find it a great idea and will thing about potential technical solutions when I find the time for it...
Best regards, Stefan
Sorry, something went wrong.
No branches or pull requests
An aggregate might be present in multiple bounded contexts, in different forms. For example, as described in https://docs.microsoft.com/en-us/dotnet/architecture/microservices/architect-microservice-container-applications/identify-microservice-domain-model-boundaries (Figure 4-10), a
User
from one bounded context can be aBuyer
in another. Could this be expressed somehow in terms of the DSL or the generators? Ideally the outcome would be something like this:The text was updated successfully, but these errors were encountered: