-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Is there a specific lint api for Dagger2 #494
Comments
Can you elaborate about what you want to be linting? |
While Dagger compile time errors work well when they are alone. They do not output anything when you integrate other annotation processors (Databinding). This makes solving errors a nightmare. It could be as simple as missing providers or incorrect dependencies but Dagger does not provide those outputs. The final output of I would like someway to separate the different annotation processors and hence get logical errors. This is what I would want to lint, Or if you think there is a better approach instead of lint ,I'd like to try that too. I understand these are compile time errors and Lint is really not needed. But any sort of static analysis could prove to be useful. |
This might be what you're looking for: #306 (comment) Doing something like linting will be very challenging - you'll essentially be trying to reimplement a lot of the dagger processor when you see an issue, but with less information. |
This does help,thanks a lot! |
I searched quite a bit, but did not come across any. If someone could point me in a direction for implementation.I could try my hand at this
The text was updated successfully, but these errors were encountered: