better documentation for package class pattern matching

[xenoterracide]

could you add a full section to the user guide that goes over how .., .(*).. .(**) etc work. I'm hoping it starts with you have this list of packages and classes. something like this

com.myorg.myapp.foo.Foo
com.myorg.myapp.foo.service.baz.BazService
com.myorg.myapp.controller.bar.BarController
com.myorg.myapp.controller.bar.baz.Baz

..controller..

would match only

com.myorg.myapp.controller.bar.BarController
com.myorg.myapp.controller.bar.baz.Baz

..baz

would match?

com.myorg.myapp.foo.service.baz.BazService
com.myorg.myapp.controller.bar.baz.Baz

..foo.(*)

would match

com.myorg.myapp.foo.Foo

I'm kind of starting to guess... I found out some of my rules weren't doing what I thought they did. I know there's a smattering of this, but I feel like it needs expansion.

For example, what if I basically want all of my code to be free of cycles? what if I don't want classes nested beyond two levels (past my org.app)? e.g. this is not legal, there may not be an additional package after "bar". note: this may require an additonal feature.

com.myorg.myapp.controller.bar.baz.Baz

[CHAND4N]

Hi! I’d like to work on adding a section to the user guide explaining .., *, and ** pattern matching with examples but would like to know where in user guide to do it should i create a new md file and add?
. Thanks!