We're experimenting with rules to enforce some com...

# konsist

[Emanuel Moecklin]

We're experimenting with rules to enforce some company standards (22 Android devs) and so far I love it (especially compared with custom Lint rules...). One of the rules we want to enforce is that Fragments need to use viewLifecycleOwner.lifecycleScope over lifecycleScope to launch a Coroutine so

// BAD
lifecycleScope.launch {
    // here goes my code
}

// GOOD
viewLifecycleOwner.lifecycleScope.launch {
    // here goes my code
}

Unfortunately both add the same import so I can't check for imports. Any ideas how this could be done?

[Yonatan Karp-Rudin]

I don't know a single thing about android, but have you considered using something like the code snippet suggested in the docs?

@Test
fun `coroutine scope usage of 'lifecycleScope.launch' in file is forbiden`() {
    Konsist
        .scopeFromProject()
        .files
        .assertFalse { it.text.contains("lifecycleScope.launch") }
}

You can see the original example here.

[Emanuel Moecklin]

ah yes that might work... let me test that thank you color

[Emanuel Moecklin]

To limit this to certain classes I will use

// matches `lifecycleScope.launch` but doesn't match `viewLifecycleOwner.lifecycleScope.launch`
private val launchRegex = "[^\\.]+lifecycleScope\\.launch".toRegex()

Konsist
    .scopeFromProject()
    .classes()
    .withAllParentsOf(Fragment::class)
    .assertFalse {
        it.text.contains(launchRegex)
    }

[igor.wojda]

BTW @Emanuel Moecklin we would like to add more Android snippets to our docs. Consider sharing some of your tests in the future when you will come up with interesting examples.