Add gradle lint#1096
Draft
Tejas2805 wants to merge 9 commits into
Draft
Conversation
Contributor
Author
|
@fzdy1914 @eugenepeh If you both think having a gradle lint is a good idea, I can try out more useful rules and apply them accordingly. Or I will just stick with PR #1095 Let me know your thoughts on it. |
Member
|
Hmm, if its a one-time thing then its better not to integrate it into the repo as it is also a plugin itself that may somewhat affect the build time. We can however, leave it as an active PR to help us detect misuse from time to time. |
Member
|
@Tejas2805, I accidentally mess up this PR, can you help fix it? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We can add a gradle lint to check unused dependencies and deprecated packages and update them accordingly.
PR #1095 was based on this