mirror of
https://github.com/vacp2p/specs.git
synced 2026-01-08 23:08:09 -05:00
Remove second-guessing naming of Message field
Small tweak, but it kept jumping out at me as I'm reading the spec. A spec should be written in an authoritative manner and not second-guess itself. Right now it reads more like a note to self that was left over. If this is a possible enhancement/renaming, it should be captured in a separate issue IMO. It is also unlikely that this field will change, considering how many clients implemented it with this naming. Finally, I personally think the name is perfectly fine :)
This commit is contained in:
@@ -99,8 +99,7 @@ false signifies 'unsubscribe'.
|
||||
|
||||
## The Message
|
||||
|
||||
The RPC message can contain zero or more messages of type 'Message' (perhaps
|
||||
this should be named better?). The Message protobuf looks like this:
|
||||
The RPC message can contain zero or more messages of type 'Message'. The Message protobuf looks like this:
|
||||
|
||||
```protobuf
|
||||
message Message {
|
||||
|
||||
Reference in New Issue
Block a user