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:
Oskar Thorén
2020-07-08 13:01:11 +08:00
committed by GitHub
parent a87e386113
commit 7b45ead06a

View File

@@ -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 {