aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul Frazee <pfrazee@gmail.com>2018-06-27 11:32:01 -0500
committerPaul Frazee <pfrazee@gmail.com>2018-06-27 11:32:01 -0500
commit1a22f614a22c1aaf04f1601390f54b8d1e214456 (patch)
treed2f5898483266e912576f3b5572debd9c3879e6c
parent913a0b6663902e6c92bb82ae968040f11bcf5b22 (diff)
downloaddat-deps-1a22f614a22c1aaf04f1601390f54b8d1e214456.tar.gz
dat-deps-1a22f614a22c1aaf04f1601390f54b8d1e214456.zip
Ignore additional fields
-rw-r--r--proposals/0000-hypercore-header.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/proposals/0000-hypercore-header.md b/proposals/0000-hypercore-header.md
index 3b44f65..7a65b3c 100644
--- a/proposals/0000-hypercore-header.md
+++ b/proposals/0000-hypercore-header.md
@@ -79,7 +79,7 @@ message HypercoreHeader {
}
```
-Data structures should not add additional fields to the `HypercoreHeader`. They should put any additional data into the `extension`. This is easy to do with protobuf's nested messages. For example:
+Data structures should not add additional fields to the `HypercoreHeader`. Any additional fields should be ignored. Data-structure-specific data can be stored in the `extension`. This is easy to do with protobuf's nested messages. For example:
```protobuf
message MyCustomHeader {