Is your feature request related to a problem? Please describe.
I've been unable to make both live together, I've tried several times without finding a way to make it work.
No-private requires elements to be recognized, so I needed to make an element-type setting for that purpose.
At the same time doing so prevents a file/directory to be matched by another element type, preventing some boundary rules to be implemented.
I thought I could use no-private thanks to the element types defined for boundaries but that do not seems to work..
Describe the solution you'd like
An repository of a working example of integration of both no-private and element-type import/export rules
Describe alternatives you've considered
I've tried to achieve it without any success
Thanks in advance that lib is a game-changer for proper architecture enforcement !
Hi @sledorze , in fact, it should work with the same element types that you use for boundaries. Could you please provide an example of configuration and file tree that you are trying to configure?
Is your feature request related to a problem? Please describe.
I've been unable to make both live together, I've tried several times without finding a way to make it work. No-private requires elements to be recognized, so I needed to make an element-type setting for that purpose. At the same time doing so prevents a file/directory to be matched by another element type, preventing some boundary rules to be implemented. I thought I could use no-private thanks to the element types defined for boundaries but that do not seems to work..
Describe the solution you'd like An repository of a working example of integration of both no-private and element-type import/export rules
Describe alternatives you've considered I've tried to achieve it without any success
Thanks in advance that lib is a game-changer for proper architecture enforcement !