-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add possibility to check flavoured android modules #143
base: master
Are you sure you want to change the base?
Add possibility to check flavoured android modules #143
Conversation
@@ -64,4 +64,10 @@ open class ApiValidationExtension { | |||
* By default, only the `main` source set is checked. | |||
*/ | |||
public var additionalSourceSets: MutableSet<String> = HashSet() | |||
|
|||
/** | |||
* In Android projects with multiple flavour, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo: flavours
* Copyright 2016-2022 JetBrains s.r.o. | ||
* Use of this source code is governed by the Apache 2.0 License that can be found in the LICENSE.txt file. | ||
*/ | ||
import org.jetbrains.kotlin.gradle.plugin.* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick: Should it follow the same rules as in other changed files for explicit imports? Or vice versa?
@qwwdfsad Is it possible to prioritise this PR? |
Does this take into account that some modules inside the project might lack flavors or the particular flavor set here?(when the plugin is configured in the root gradle file) My suggestion would be to generate unique tasks for each flavor, similar to other gradle plugins compatible with flavors. |
Fair, I don't think I have checked that, let's try |
Added the option to test flavoured android modules thanks to
testedFlavourName
parameterit would solve #24