Skip to content
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

Improve code quality #6

Open
rodrigoalvesvieira opened this issue Apr 13, 2013 · 3 comments
Open

Improve code quality #6

rodrigoalvesvieira opened this issue Apr 13, 2013 · 3 comments

Comments

@rodrigoalvesvieira
Copy link

This is not a to-do that might be done ASAP, but a continuous task and - in general - we should aim at making the code easier to maintain (even if we assume that there is not thousands of people interested)

The Oracle's Code Conventions for the Java TM Programming Language is a nice guide that might help us with this continuous task.

@rodrigoalvesvieira
Copy link
Author

There is something else related to this issue that we can work to improve too: replace System.out.print/println calls with logger.info calls, which are actually appropriate for logging.

@gustavopinto
Copy link
Member

Other point: the extractor package has the Uncompressor interface, but no one class in this package are implementing it. Or remove the interface, which, I think, is not a good idea, or force all classes to implement it.

@rodrigoalvesvieira
Copy link
Author

Interesting, hadn't noticed this before. I agree with forcing the implementation.

rodrigoalvesvieira pushed a commit that referenced this issue Apr 27, 2013
…ing unnecessary blank spaces/lines. Related to #6 and #20.
rodrigoalvesvieira pushed a commit that referenced this issue May 4, 2013
…ding 'this' to the references to local object's properties. Related to #6 and #20.
gustavopinto pushed a commit that referenced this issue May 17, 2013
gustavopinto pushed a commit that referenced this issue May 17, 2013
rodrigoalvesvieira pushed a commit that referenced this issue Jun 13, 2013
rodrigoalvesvieira pushed a commit that referenced this issue Jul 5, 2013
Sometimes the attribute name in the API differs from the attribute name in its correspondent class in Groundhog. Using SerializedName we can manage to solve any issues regarding these differences

More info at http://google-gson.googlecode.com/svn/tags/1.2.3/docs/javadocs/com/google/gson/annotations/SerializedName.html

Related to #6
rodrigoalvesvieira pushed a commit that referenced this issue Jul 5, 2013
…his attribute duplicates the watchersCount one.

Related to #6
gustavopinto pushed a commit that referenced this issue Jul 16, 2013
rodrigoalvesvieira pushed a commit that referenced this issue Jul 18, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants