Setup Konsist module for enforcing architectural constraints

[yesshreyes]

No description provided.

[RajashekarRaju]

You missed 2 things

1. Ktlint

I believe checks are not happening in this new module, check why.

2. Guarding your screens by identifying which components are not declared

You know none of your screen code is still calling those wrappers directly. But there are dozens of other Material 3 APIs (e.g. AlertDialog, TopAppBar, TextButton, etc.) that also need to live in your design-system. To catch any you’ve missed, add a “global coverage” test:

@Test
fun `all material3 components have design-system wrappers`() {
    val ignoreComponents = setOf(
        "androidx.compose.material3.Typography",
    )

    checkAllMaterial3ComponentsMoved(
        allowedComponents = ignoreComponents,
        excludePaths = arrayOf(DESIGN_SYSTEM_PATH)
    )
}

And in your KonsistUtils.kt, add the helper that this test calls:

internal fun checkAllMaterial3ComponentsMoved(
    allowedComponents: Set<String>,
    excludePaths: Array<String> = emptyArray(),
) {
    val files = Konsist
        .scopeFromProject()
        .files
        .filter { file ->
            val path = file.path.replace("\\", "/").lowercase()
            excludePaths.none { path.contains(it.replace("\\", "/").lowercase()) }
        }

    val allMaterial3Imports = files
        .flatMap { it.imports }
        .map { it.name }
        .filter { it.startsWith("androidx.compose.material3.") }
        .distinct()

    val pending = allMaterial3Imports - allowedComponents

    assertTrue(
        actual = pending.isEmpty(),
        message = "Found pending Material3 components not in design-system:\n" +
                pending.joinToString("\n") { "  • $it" },
    )
}

• excludePaths makes sure you don’t flag your own wrapper files.
• allowedComponents is really an “ignore list” for things you don’t plan to wrap (typography, themes, annotations, etc.)

With this in place, every time you run your Konsist suite you’ll get a clear list of any Material 3 APIs still living in your app code rather than in design-system.

You can also guard from others declaring their own components, this is more like building a fool proof for your tests.