Go kosu/rpc docs

[gchaincl]

Overview

Updates the code comments and add requires support to generate rpc documentation

ATM, doc generation is very rudimentary:
go to ./rpc/doctool and run:

go run main.go ../ > ../../../kosu-docs/docs/kosu-rpc/methods.md

[hrharder]

It is ideal to output the docs for each package within the monorepo to a PACKAGE-NAME/docs folder, so then the kosu-docs package build process can be automated to pull in docs from each package.

Can we move the generated markdown to go-kosu/docs? Other than that, everything looks good!

[hrharder]

Looks like you may have already moved the doc, so my comment above may no longer be relevant! looks like there are still some linting checks that are failing 🤷‍♂

[gchaincl]

should we keep all docs under go-kosu/docs or go-kosu/<module>/docs is better?

[hrharder]

hmmm... unless there is reason to do go-kosu/<module>/docs I think go-kosu/docs/<module>/files would be better, as it lines up with how it works in other repos.

is that ok?

[hrharder]

it also seems like the full go-kosu tests never ran on #174, so the build looks like it passed when really the go-kosu tests are failing (meaning the master branch is now broken)

Nick and I are examining and seeing if we can change how the changeset plugin works