This doesn't affect the text output, which was already using a
stringified name. The earlier stringification does change the JSON
output from an enumeration integer (e.g. 2) to the string form
(e.g. "File"). If/when we transition to Merkle-object types named by
their hash, we will probably want to revisit this and pass both the
type hash and human-readable-but-collision-prone name on to clients.
License: MIT
Signed-off-by:
W. Trevor King <wking@tremily.us>
| 名称 |
最后提交
|
最后更新 |
|---|---|---|
| .. | ||
| commands | 正在载入提交数据... | |
| corehttp | 正在载入提交数据... | |
| corenet | 正在载入提交数据... | |
| corerepo | 正在载入提交数据... | |
| corerouting | 正在载入提交数据... | |
| coreunix | 正在载入提交数据... | |
| mock | 正在载入提交数据... | |
| .gitignore | 正在载入提交数据... | |
| bootstrap.go | 正在载入提交数据... | |
| bootstrap_test.go | 正在载入提交数据... | |
| builder.go | 正在载入提交数据... | |
| core.go | 正在载入提交数据... | |
| core_test.go | 正在载入提交数据... | |
| pathresolver.go | 正在载入提交数据... | |
| pathresolver_test.go | 正在载入提交数据... |