You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lint is not generating a baseline.xml when using the Lint task from this plugin. The issue seems to that the baseline file is being configured in library modules as well, whereas instead it should only be done for Application Modules. Adding a
if (androidExtensionNullable is ApplicationAndroidComponentsExtension)
before configuring the baseline file seems to resolve the issue. Given checkDependencies is enabled for app modules, it makes sense to enable baseline also just for app modules.
I have this working locally and can send a PR if you are open to contributions and agree with the change. Didn't file it under discussion as it was more of a bug than a feature request :)
The text was updated successfully, but these errors were encountered:
I'm not sure I follow this. We run lint with baselines on both library and application projects. In our application project, we only run lint with UnusedResources and nothing else. Could you elaborate on why you think this option only applies to application projects?
https://github.com/slackhq/slack-gradle-plugin/blob/2670eb302109c6b15f60008d1314802b144c5427/slack-plugin/src/main/kotlin/slack/gradle/lint/LintTasks.kt#L341
Lint is not generating a baseline.xml when using the Lint task from this plugin. The issue seems to that the baseline file is being configured in library modules as well, whereas instead it should only be done for Application Modules. Adding a
before configuring the baseline file seems to resolve the issue. Given
checkDependencies
is enabled for app modules, it makes sense to enable baseline also just for app modules.I have this working locally and can send a PR if you are open to contributions and agree with the change. Didn't file it under discussion as it was more of a bug than a feature request :)
The text was updated successfully, but these errors were encountered: