BUG: `ComposeCompositionLocalUsage` does not use `allowed-composition-locals` option correctly.

[Staartvin]

In my project I have the following code:

val LocalColors = staticCompositionLocalOf { Colors() }

when I add an exemption to my lint.xml like so:

<issue id="ComposeCompositionLocalUsage">
   <option name="allowed-composition-locals" value="LocalColors" />
</issue>

The linter will still complain:
Error: CompositionLocals are implicit dependencies and creating new ones should be avoided

[ZacSweers]

Please link a minimally reproducible sample, this isn't enough information to help

[Staartvin]

While generating an example project, it seems that the error occurs when the CompositionLocal definition is in one Android gradle module, while the lint.xml is the app module. If I have add a CompositionLocal definition (that ought to be flagged by the linter) in the app module it is correctly ignored, but when I add it in another module the definition does not get ignored.

I've attached an example project with two separate modules (app and another_module) where the staticCompositionLocalOf = {} is defined in another_module and the lint.xml file is located in the app module. Try running ./gradlew lint to see that the linter still gives an error.

TestApplicaiton.zip

Note: If I ignore the issue using:

<issue id="ComposeCompositionLocalUsage" severity="ignore" />

in the lint.xml it will correctly ignore the warning.

[ZacSweers]

Lint.xml files work hierarchically like .gitignore files if not specified directly in the lint gradle DSL. I'm not at a computer but I would check that you're using them correctly

[Staartvin]

I can confirm that if I place the lint.xml in the root of the project, it seems to recognize it. However, what is contradicting this finding, is that ignoring an issue in a lint.xml placed in the app module will ignore the issue even though it's generated in another module.