go packages which are fine
Go to file
2018-08-13 19:40:41 -04:00
cmd/totp-proxy totp-proxy: add Dockerfile 2018-08-09 18:42:59 -06:00
jstream mtest->mrand: move rand functionality from mtest into its own package 2018-07-03 00:20:00 +00:00
m m: add TODO to figure out wtf to do about m.Log 2018-07-19 19:37:05 +00:00
mcfg mcfg: implement SourceEnv, and move a bunch of code it shares with SourceCLI to source(_test).go 2018-08-13 19:40:41 -04:00
mcrypto mcrypto: fix docs a bit 2018-08-09 18:04:39 -06:00
mdb mbigtable: implement basic cfg and basic tests 2018-07-21 19:56:50 +00:00
mhttp mhttp: implement ReverseProxy 2018-08-09 14:02:11 -06:00
mlog mlog: change how Merge/MergeInto work, so they don't evaluate the KV immediately 2018-07-19 18:43:17 +00:00
mnet mnet: implement IsReservedIP 2018-08-09 12:34:09 -06:00
mrand mrand: fix bug in Hex with it not outputting correct number of characters for odd number inputs 2018-08-13 19:40:15 -04:00
mrpc mtest->mrand: move rand functionality from mtest into its own package 2018-07-03 00:20:00 +00:00
mtest mchk: move mtest.Checker to mtest/mchk, and refactor its types a little bit 2018-08-13 15:03:30 -04:00
mtime mtime: fix older package doc not having been deleted 2018-05-27 07:57:23 +00:00
env.test mbigtable: implement basic cfg and basic tests 2018-07-21 19:56:50 +00:00
LICENSE Initial commit 2018-01-11 15:47:01 +00:00
README.md README: add styleguide section 2018-03-26 10:54:01 +00:00

mediocre-go-lib

This is a collection of packages which I use across many of my personal projects. All packages intended to be used start with an m, packages not starting with m are for internal use within this set of packages.

Other third-party packages which integrate into these:

  • merry: used by mlog to embed KV logging information into error instances, it should be assumed that all errors returned from these packages are merry.Error instances. In cases where a package has a specific error it might return and which might be checked for a function to perform that equality check will be supplied as part of the package.

Styleguide

Here are general guidelines I use when making decisions about how code in this repo should be written. Most of the guidelines I have come up with myself have to do with package design, since packages are the only thing which have any rigidity and therefore need any rigid rules.

Everything here are guidelines, not actual rules.