-
Notifications
You must be signed in to change notification settings - Fork 229
Coding guidelines
せいうはん edited this page Mar 19, 2018
·
6 revisions
These guidelines are written, not only to make the code base more consistent, but also to make it easier for the project collaborators to merge pull requests from the contributors.
- Use spaces, not tabs.
- Use 4 spaces to indent.
- Lines should not contain trailing spaces.
- Use US English names for all variables, functions and classes.
- Don't use underscore for private variables. Example:
myVariable
instead of_myVariable
.
- Do not leave unused
import
statements.
- ... you only changed the code you intended to change. If you have added whitespace characters or in any other way changed code that is not a part of your particular fix, the pull request will not get merged. So please check your pull request before submitting. If you see something unrelated that needs to be cleaned up, fix it in a separate pull request.
- ... the code you just wrote has decent test coverage.
Contributing
Documentation
- Configuration
- Fetching data from database
- Fetching data lazily
- Column mappings
- Updates and inserts
- Transactions
- Running queries in a batch
- Integration with Spring Framework
- Register custom converters
- Sql2o on Android
Other resources