《How to improve quality and syntax of your Android code》翻译初稿完成 #92
Conversation
This file contains 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
| * [ The one in the root folder](https://github.com/vincentbrison/vb-android-app-quality/blob/master/build.gradle), which is more or less just about configuration for the project (which maven repos to use, which Gradle version to use….). | ||
| * [The one in the subfolder app](https://github.com/vincentbrison/vb-android-app-quality/blob/master/app/build.gradle), which is a very classic gradle file to build an Android application. | ||
| * [The one in the subfolder config](https://github.com/vincentbrison/vb-android-app-quality/blob/master/config/quality.gradle), on which we will focus on, since I use this one to retain and configure all my quality tools for my project. | ||
| ## 关于我demo项目的层次 |
Closed
|
@laobie 请问对这篇文章没有修改意见么？ |
|
@Glowin 我明天看下，今天在搬家😂 |
|
|
||
| In this article, I will present different ways of improving your Android code with automatic tools such as [Checkstyle](http://checkstyle.sourceforge.net/), [Findbugs](http://findbugs.sourceforge.net/), [PMD](http://pmd.sourceforge.net/), and of course [Android Lint](http://tools.android.com/tips/lint). Test your code in an automated way can be very useful, especially when you are working with teammates, in order to maintain a rigorous syntax through your code, and avoid a lot of bad practices and errors. I will explain precisely how to use these tools directly through your Gradle build script, and how to configure them at your convenience. | ||
| 在这篇文章中，我会介绍几种不同的方式，让你通过自动化工具提高你的Android代码质量，包括 [Checkstyle](http://checkstyle.sourceforge.net/)， [Findbugs](http://findbugs.sourceforge.net/)， [PMD](http://pmd.sourceforge.net/)， 当然，还有我们最熟悉的[Android Lint](http://tools.android.com/tips/lint)。 使用自动化的方式测试你的代码十分有用，尤其当你处于团队工作中，并想让你代码维持缜密的语法，同时避免一些糟糕的实践和错误时。我会细心地解释如何直接通过你的Gradle构建脚本使用这些工具，并方便地配置它们。 |
There was a problem hiding this comment.
“使用自动化的方式测试你的代码十分有用，尤其当你处于团队工作中，并想让你代码维持缜密的语法，同时避免一些糟糕的实践和错误时。我会细心地解释如何直接通过你的Gradle构建脚本使用这些工具，并方便地配置它们。”
建议改成：
“为了让你的代码保持缜密的语法，同时避免一些糟糕的实现和错误，使用自动化的方式测试你的代码十分有用，尤其是当你和队友一起工作时。我会细心地解释如何直接通过你的Gradle构建脚本使用这些工具，和怎么方便地配置它们。”
There was a problem hiding this comment.
这个翻译很赞.最不好翻译的就是这些长句.谢谢
|
@Glowin 审核完成 |
|
@laobie 已经根据你的建议修改提交,感谢校对 |
|
@yinshudi 不客气2333 |
Glowin
added a commit
that referenced
this pull request
Jan 27, 2016
《How to improve quality and syntax of your Android code》翻译初稿完成
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
RT