grpc / grpc/grpc-java

Fix lint issues in Android projects

Offen
#7,734 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
android code health
Vorherrschende Sprache
Java
Sterne
12.1k
Forks
4k
Ø Merge
2 T. 17 Std.
Gemergte PRs (30 T.)
37

Beschreibung

It seems we aren't targeting the a recent Android version. Many of the CheckResult failures appear to be expected behavior, so it will need to be silenced in some way. There's some warnings about old versions and some UI goo. Quite a mixed bag. I'm fine if we resolve a substantial portion of them with this issue and open separate issues for the remaining items.

```
> Task :grpc-android:lint
Ran lint on variant debug: 1 issues found
Ran lint on variant release: 1 issues found
Wrote HTML report to grpc-java/android/build/reports/lint-results.html
Wrote XML report to grpc-java/android/build/reports/lint-results.xml

> Task :grpc-cronet:lint
Ran lint on variant debug: 1 issues found
Ran lint on variant release: 1 issues found
Wrote HTML report to grpc-java/cronet/build/reports/lint-results.html
Wrote XML report to grpc-java/cronet/build/reports/lint-results.xml

> Task :grpc-android-interop-testing:lint
Ran lint on variant release: 64 issues found
Ran lint on variant debug: 64 issues found
Wrote HTML report to grpc-java/android-interop-testing/build/reports/lint-results.html
Wrote XML report to grpc-java/android-interop-testing/build/reports/lint-results.xml
```

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Start by running lint for grpc-android, grpc-cronet, and grpc-android-interop-testing, then inspect the generated reports under android/build/reports and the corresponding module reports. Group the CheckResult, old-version, and UI warnings by cause and identify which can be silenced safely. Done means resolving a substantial, documented portion of the reported issues and separating the remaining work into follow-up issues.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
android, java
Bereich
build-system, mobile
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.