IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2024-11-28 03:34:15 -06:00
Code Issues Packages Projects Releases Wiki Activity
2e350bbb8e
grafana/vendor/github.com/Unknwon/com
History
Torkel Ödegaard 4720216e5e tech: upgraded macaron & macaron inject, binding, session
2017-04-25 15:16:32 +02:00
..
testdata tech(build): move dependencies to vendor folder 2016-09-14 16:14:27 +02:00
cmd.go tech(build): move dependencies to vendor folder 2016-09-14 16:14:27 +02:00
convert.go tech: upgraded macaron & macaron inject, binding, session 2017-04-25 15:16:32 +02:00
dir.go tech(build): move dependencies to vendor folder 2016-09-14 16:14:27 +02:00
file.go tech(build): move dependencies to vendor folder 2016-09-14 16:14:27 +02:00
html.go tech(build): move dependencies to vendor folder 2016-09-14 16:14:27 +02:00
http.go tech(build): move dependencies to vendor folder 2016-09-14 16:14:27 +02:00
LICENSE tech(build): move dependencies to vendor folder 2016-09-14 16:14:27 +02:00
math.go tech: upgraded macaron & macaron inject, binding, session 2017-04-25 15:16:32 +02:00
path.go tech: upgraded macaron & macaron inject, binding, session 2017-04-25 15:16:32 +02:00
README.md tech: upgraded macaron & macaron inject, binding, session 2017-04-25 15:16:32 +02:00
regex.go tech(build): move dependencies to vendor folder 2016-09-14 16:14:27 +02:00
slice.go tech(build): move dependencies to vendor folder 2016-09-14 16:14:27 +02:00
string.go tech: upgraded macaron & macaron inject, binding, session 2017-04-25 15:16:32 +02:00
time.go tech(build): move dependencies to vendor folder 2016-09-14 16:14:27 +02:00
url.go tech(build): move dependencies to vendor folder 2016-09-14 16:14:27 +02:00

README.md

Common Functions

Build Status Go Walker

This is an open source project for commonly used functions for the Go programming language.

This package need >= go 1.2

Code Convention: based on Go Code Convention.

Contribute

Your contribute is welcome, but you have to check following steps after you added some functions and commit them:

  1. Make sure you wrote user-friendly comments for all functions .
  2. Make sure you wrote test cases with any possible condition for all functions in file *_test.go.
  3. Make sure you wrote benchmarks for all functions in file *_test.go.
  4. Make sure you wrote useful examples for all functions in file example_test.go.
  5. Make sure you ran go test and got PASS .