I have an interesting use-case - and it's :100:% p...

# konsist

[Yonatan Karp-Rudin]

I have an interesting use-case - and it's 💯% possible that I'm just abusing the system here...
I have my architecture broke down into multiple Gradle module in my repo:
• model
• application
• adapter
• bootstrap (as it's running on plain Kotlin ATM)
I wanted to write the e2e and architecture tests on the bootstrap module, and noticed that it discovers only the model dependencies during the following:

Konsist
    .scopeFromProject()
    .classes()

I wonder if there's a way to enforce it to scan the entire project and not just the module (and it's dependencies)? or is it the wrong place to make such a design? 🤔