uber/okbuck

Enable lints that use project structure and merged manifest

Open

#545 opened on Oct 23, 2017

View on GitHub
 (0 comments) (3 reactions) (0 assignees)Java (1,533 stars) (180 forks)batch import
enhancementhelp wanted

Description

In Lint 26.x, the command line lint that Buck uses has a --project option that lets you specify an XML file describing the project being linted. ProjectInitializer.kt describes how the XML file is parsed and what options are supported. It may be possible to construct the XML project file such that lints that use the presence/absence of the support library and permissions merged from dependent module manifests would be able to work again

Contributor guide

Tech stack
javakotlin
Domain
build systemtooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
JavaKotlinBuck build systemAndroid Lint
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate ProjectInitializer.kt to understand how the XML project file is parsed and what options are supported. Then determine how to construct the XML file to enable lints that check for support library presence and permissions from merged manifests. There are no comments or linked PRs to guide the implementation. Start by reading the Buck documentation on lint configuration.