dc0e8de9b0
so they can be used in rpc/core/types/responses.go.
```
So, it seems like we could use the actual structs here, but we don't want to have to import consensus to get them, as then clients are importing too much crap. So probably we should move some types from consensus into consensus/types so we can import.
Will these raw messages be identical to:
type ResultDumpConsensusState struct {
RoundState cstypes.RoundState
PeerRoundStates map[string]cstypes.PeerRoundState
}
```
https://github.com/tendermint/tendermint/pull/724#discussion_r143598193
|
||
|---|---|---|
| .. | ||
| types | ||
| README.md | ||
| abci.go | ||
| blocks.go | ||
| consensus.go | ||
| dev.go | ||
| doc.go | ||
| doc_template.txt | ||
| events.go | ||
| mempool.go | ||
| net.go | ||
| pipe.go | ||
| routes.go | ||
| status.go | ||
| tx.go | ||
| version.go | ||
README.md
Tendermint RPC
Generate markdown for Slate
We are using Slate to power our RPC documentation. If you are changing a comment, make sure to copy the resulting changes to the slate repo and make a PR there as well. For generating markdown use:
go get github.com/melekes/godoc2md
godoc2md -template rpc/core/doc_template.txt github.com/tendermint/tendermint/rpc/core | grep -v -e "pipe.go" -e "routes.go" -e "dev.go" | sed 's$/src/target$https://github.com/tendermint/tendermint/tree/master/rpc/core$'