Background
#37 was created to support the scenario where a single bounded context is split into multiple repositories. We don't want to copy the term definitions associated with the context into all the repositories, so it is looking for a way to define them in one source repo and distribute/share them out to working environments when working in other repositories.
Feature Idea
This ticket builds on that idea by supporting the notion of sharing from multiple sources. e.g. a repository for an 'app' that includes code associated with terminology from multiple bounded contexts, where the context definitions have been split up and are in other locations as per #37.
While this repository layout pattern is not recommended, it is a reality that some teams will be in that situation and we'd still like to help them get access to clearer definitions of the domain concepts they're working with.
This feature could also be useful in a repo per context configuration if you would like to have visibility of the usage of the same terminology in other contexts as a way of aiding clarity on the distinction between the usage in each context.
Background
#37 was created to support the scenario where a single bounded context is split into multiple repositories. We don't want to copy the term definitions associated with the context into all the repositories, so it is looking for a way to define them in one source repo and distribute/share them out to working environments when working in other repositories.
Feature Idea
This ticket builds on that idea by supporting the notion of sharing from multiple sources. e.g. a repository for an 'app' that includes code associated with terminology from multiple bounded contexts, where the context definitions have been split up and are in other locations as per #37.
While this repository layout pattern is not recommended, it is a reality that some teams will be in that situation and we'd still like to help them get access to clearer definitions of the domain concepts they're working with.
This feature could also be useful in a repo per context configuration if you would like to have visibility of the usage of the same terminology in other contexts as a way of aiding clarity on the distinction between the usage in each context.