Repository navigation
Slice matching does not group classes of subnamespaces into the correct slice #208
Description
Given these example dependencies:
Module.One.Class1 -> Module.Two.Class1
Module.Two.Class2 -> Module.One.Class1
a slice rule of Slices().Matching("Module.(*)").Should().BeFreeOfCycles() finds the dependency cycle.
However, if you move Class2 into a sub-namespace, the cycle no longer gets detected:
Module.One.Class1 -> Module.Two.Class1
Module.Two.InnerNamespace.Class2 -> Module.One.Class1
Activity
[-]Slice matching ignores subnamespaces[/-][+]Slice matching does not group classes of subnamespaces into the correct slice[/+]ce-bo commentedon Mar 5, 2026
Hello everyone, I would like to know if you are planning to address this bug. Thank you!
alexanderlinne commentedon Mar 15, 2026
Hi @ce-bo, I already have a patch that aligns the implementation of slices with ArchUnit and should fix this issue. I haven't finished creating a PR for that since it's a breaking change for some cases with how slices are currently matched. Also theres some implementation details I have to work on. I'm planning to get this ready for 0.14.0 but can't give you a timeline right now.
ce-bo commentedon Mar 15, 2026
Great news, thank you @alexanderlinne!
Let me know as soon as you need test feedback.
test: move slice fixtures into a dedicated SlicesTestAssembly
feat: match slice patterns with regex like ArchUnit
test: move slice fixtures into a dedicated SlicesTestAssembly
test: move slice fixtures into a dedicated SlicesTestAssembly
feat: match slice patterns with regex like ArchUnit
feat: match slice patterns with regex like ArchUnit
feat: match slice patterns with regex like ArchUnit