Are y'all taking contributions for DCL? There's a ...
# declarative-gradle
j
Are y'all taking contributions for DCL? There's a few things that are very small and straightforward like SARIF reports for Android Lint, and bigger things like Kotlin Inject, signing configuration for debug/release variants
It looks from the contributing page that the only ask is about improving documentation, happy to do that if that's what helps
j
It might be a bit early for external contributions at this stage, considering how experimental the whole initiative still is, but if you feel strongly about specific things feel free to describe them in some details and we can for sure at least talk about them.
馃憤 1
j
I'd start with just Android Lint - the extension currently reads a few fields, so a configuration such as this isn't currently possible:
Copy code
lint {
        sarifOutput = file("${layout.buildDirectory.get()}/reports/lint-results.sarif")
        htmlOutput = file("${layout.buildDirectory.get()}/reports/lint-results.html")
    }
While Lint has a ton of options for configuration I think it can be beneficial to add a couple of these output options instead of just the Boolean for xml report. I've experimented with running DCL in my android build repo on GitHub and found these are the 3 things that would hold back demoing DCL build improvements
I wouldn't want to boil the ocean with every possible option, just add the output path ones
If that goes well my next targeted improvement would be adding support for Android signing configs as quite necessary for DCL to be able to used for actual Android builds. It also enables UI tests in ci with fan in builds, which would be the other piece I'd want to demo in a DCL based CI experiment.
Overall this should let people see what the improvement is and that things like config cache and project isolation still work (I already have that working today)
p
DCL doesn't support assigning properties of files/directory types yet. As described in the public roadmap this is planned to ship in february. We are actively working on this. This is required for both lint and signing.
馃憤 1