-
Notifications
You must be signed in to change notification settings - Fork 10
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
Style #8
Conversation
@Clever/engineers Please review. |
* Avoids holy wars over small details, but still encourages an approach to coding that sweats the details. | ||
|
||
For each of the languages below we link to a style guide reference and outline tools to use in order to help follow the style guide. | ||
These tools should be part of every project's build and test cycle. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume this means moving style checking to be triggered by make
and/or make test
(since that's how all of our projects build/test). We've discussed this as an alternative to git pre-commit hooks before and I like the idea!
Maybe this section could benefit from a short explanation of why style checking should be part of the build and test cycle as opposed to other options (e.g. running checks ad hoc, running them in git hooks).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
||
* sublime: Add [GoSublime](https://github.com/DisposaBoy/GoSublime) for code highlighting and `go fmt` on save. | ||
|
||
* vim (TODO) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
merging! |
No description provided.