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
{{ message }}
This repository was archived by the owner on Mar 28, 2026. It is now read-only.
Two different people create two separate systems in two different git repos.
They both define that they communicate:
Architect of A defines that A->B "action".
Architect of B defines that A->B "action" (action is the same, obviously).
When I include both dsl files into my space to give readers an overview of all systems of my department, dear Structurizr complains of a (complete) duplicate.
Please consider a property to ignore these conflicts: say, ignoreDuplicateRelationships, default false.
Then each A and B architects could have errors in case they have local conflicts.
But for overall picture one could turn ignoreDuplicateRelationships=true and be happy?
Priority
I have no budget and there's no rush, please add this feature for free
Description
Two different people create two separate systems in two different git repos.
They both define that they communicate:
When I include both dsl files into my space to give readers an overview of all systems of my department, dear Structurizr complains of a (complete) duplicate.
Please consider a property to ignore these conflicts: say,
ignoreDuplicateRelationships, defaultfalse.Then each A and B architects could have errors in case they have local conflicts.
But for overall picture one could turn
ignoreDuplicateRelationships=trueand be happy?Priority
I have no budget and there's no rush, please add this feature for free
More information
(thanks for AWESOME product!)