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.

Sign up for GitHub

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

Jump to bottom

Code organization and API naming convention. #1

Closed
aofei opened this issue Nov 19, 2016 · 0 comments
Closed

Code organization and API naming convention. #1

aofei opened this issue Nov 19, 2016 · 0 comments

Comments

@aofei
Copy link
Owner

aofei commented Nov 19, 2016 •
edited

Writing Format

  1. 100 characters per line.
  2. Use <Tab> to indentation.
  3. A <Tab> occupies 8 spaces.
  4. Use // to comment.

Code Organization

  1. Use gofmt to format all go files before git commit.

Testing

  1. Use go test to test whether the Air can server properly.
Repository owner locked and limited conversation to collaborators Nov 19, 2016
@aofei aofei closed this as completed May 13, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aofei