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 style #22

Closed
pelletier opened this issue Aug 23, 2014 · 2 comments
Closed

Improve code style #22

pelletier opened this issue Aug 23, 2014 · 2 comments
Labels
feature Issue asking for a new feature in go-toml.

Comments

@pelletier
Copy link
Owner

We should follow this style guide. Current errors can be detected with a linter.

@eanderton
Copy link
Contributor

i'll keep an eye out for these style points when staging new merge requests. Good idea.

@pelletier
Copy link
Owner Author

@eanderton Nice! I am waiting for you to merge #21 before working on that, because I don't want to introduce painful merging failures.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Issue asking for a new feature in go-toml.
Projects
None yet
Development

No branches or pull requests

2 participants