-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Difficulty excluding some generated code #690
Comments
Unfortunately they don't want to spread the exclusion of annotated classes to their inner classes. That being said, I have exactly the same issue, and even more "conventional" way of excluding this nasty inner class
|
You can exclude them by name:
|
Also, like I mentioned in my description I agree that excluding annotated classes probably shouldn't exclude inner classes if they're not annotated but I do think kover need to add a mechanism for excluding based on parent annotation to allow excluding these types of files |
Oh yes I was confused between |
Hi, Could you give an example of nested classes other than |
I ignored all hilt classes by these lines (until better solution):
|
Describe the bug
Dagger generates code that looks like this:
We exclude this by excluding classes annotated by
@Generated
and@DaggerGenerated
. The issue is the innerInstanceHolder
class which isn't annotated.Expected behavior
I'm not sure I'd honestly expect it to exclude this class since it's not annotated, but most code generation frameworks will only annotate the top class and most people will want to exclude the inner class too so there should be some mechanism for excluding these.
Reports
Environment
0.9.0-RC
8.10.2
The text was updated successfully, but these errors were encountered: