NativeScript / NativeScript/android
Provide verbose metadata filtering output
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 563
- Forks
- 144
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 14
Description
Currently, there is no information about why a given class is whitelisted or blacklisted by the metadata generator.
It would be great if we provide such information when a Gradle build is performed with the --debug flag.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the metadata generator and the Gradle entry point used when building with --debug. Trace how classes are whitelisted or blacklisted and where diagnostic output is emitted. Done means the generator explains each filtering decision during a debug Gradle build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- build-system, mobile-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100