How do I set up dependency rules for DDD'esque repo?

[sdurnov]

Hi! I struggle to set up enforce module boundaries rule in NX, so I decided to try out this lib, but it seems that it also doesn't support the use case I need.
Basically, I need type:app to be able to depend on type:api and type:shell libs in scope:*, but at the same time - type:ui, type:util in scope:shared. The problem already starts here - I have no idea how to describe it with current rule settings from your docs.
Similar stuff - I have those rules of different types of libs can or cannot depend on each other within the domain, but I also need to not allow them to depend on anything in other domains other than type:api, and type:* in shared.

Any way to do that?
Though initially that I'll be able to achive that with functions, but they only give 1 tag at time, and you can't use logical expressions in rules, which makes it kinda almost useless

[rainerhahnekamp]

That sounds very complicated. Can you create an issue?

I think in your case, the best thing to do is give you an option for a function that provides all the context, so you can programmatically implement it.

[sdurnov]

That sounds very complicated. Can you create an issue?

I think in your case, the best thing to do is give you an option for a function that provides all the context, so you can programmatically implement it.

Actually, pretty typical setup, pretty much what was described in Manfred's DDD articles with minor project specifics. Anyway, yes, I guess it would be better to implement it with the function. Though, it might not be enough, because as I remember, if you have several tags in source, and several tags in target, function gives you just one at time, which doesn't allow to check on combination. Anyway, I'll describe in the issue then, thanks.

[rainerhahnekamp]

function gives you just one at time, which doesn't allow to check on combination.

That's why I asked you to create an issue. That function will then receive all source and destination tags.👍