Skip to content

Commit 327f69a

Browse files
authored
specify required field order
[email protected] specifies two accepted exact orderings for message fields.
1 parent 261fb6d commit 327f69a

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

index.html

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -833,6 +833,7 @@ <h5>Implementations</h5>
833833
<li>One space after the colon <code>:</code> for dictionary keys.</li>
834834
<li>Strings and numbers formatted according to the sections <em><a href="https://www.ecma-international.org/ecma-262/6.0/#sec-quotejsonstring">QuoteJSONString</a></em> and <em><a href="https://www.ecma-international.org/ecma-262/6.0/#sec-tostring-applied-to-the-number-type">ToString Applied to the Number Type</a></em>.
835835
<li>No trailing newline.</li>
836+
<li>The properties must be in an accepted order, no extra fields are permitted. Either <code>previous, author, sequence, timestamp, hash, content, signature</code> or <code>previous, sequence, author, timestamp, hash, content, signature</code>. (<code>author</code> and <code>sequence</code> are accepted in either order, but it's strongly recommended to put author first.</li>
836837
</ul>
837838
<aside>
838839
<p>Dictionary keys can appear in any order you choose, however the order needs to be remembered for later.</p>

0 commit comments

Comments
 (0)