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
Any layer can be included in several groups. For example, layer CBB is included into GroupB, GroupC, GroupAB, GroupCX groups.
Ruleset for groups should be merged. For example, XAX can use all allowed dependencies from both rules GroupA: [GroupAB, CCX] and GroupX: [GroupA, BBB], because XAX is included into both GroupA and GroupX.
Real example, one of many actually: we have dozens separated APIs. Each concrete API is a separate layer, so dependencies between them are forbidden. And we have common dependencies we would like to allow for all these API layers, now we have to write a massive ruleset:
For projects with huge number of layers, it would be useful to allow group layers. Something like this:
Notes:
GroupB
,GroupC
,GroupAB
,GroupCX
groups.GroupA: [GroupAB, CCX]
andGroupX: [GroupA, BBB]
, because XAX is included into both GroupA and GroupX.Real example, one of many actually: we have dozens separated APIs. Each concrete API is a separate layer, so dependencies between them are forbidden. And we have common dependencies we would like to allow for all these API layers, now we have to write a massive ruleset:
More clear version could be:
The text was updated successfully, but these errors were encountered: