android / android/architecture-samples

Excessive Auto-Generated Files and Cleanup Process in Hilt-Integrated

Open
#977 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Kotlin
Stars
45.8k
Forks
11.9k
PR merge metrics
No merged PRs in 30d

Description

In your Android project, you have been using Hilt successfully for dependency injection. However, over time, I've noticed that an excessive number of auto-generated files related to Hilt have accumulated in your project directory. These files clutter your project structure, making it difficult to manage and maintain.

![image](https://github.com/android/architecture-samples/assets/68209547/beea2e49-9069-4289-87a2-f201254ef68a)

We would greatly appreciate your guidance on how to effectively remove all unnecessary auto-generated files related to Hilt from our project and prevent them from reappearing. Additionally, any insights into why these files are persisting after removing Hilt dependencies would be valuable.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the Hilt dependency configuration in the Android project and the generated files shown in the issue image. Determine whether the files are build outputs, check what remains after removing Hilt dependencies, and document the cleanup and prevention steps. Done means the guidance explains why the files persist and how to remove or avoid them.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
build-system, mobile
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.