"field_order"=<integer> for message fields and frame layers

[dodohand]

Hello,

The Setup:

I ran right into the issue you've raised as pantor/inja#213... but wouldn't like to stop and wait for an inja fix.

The Punchline:

Have you considered a key:value pair like "field_order"=0 as part of the message fields and the frame layers so that
they can be put into the intended/required order in documentation? This would also go toward addressing the basic
fact that JSON is unordered by definition. I'm not sure that inja would permit a nice syntax for taking advantage of
this field, but it should allow successful parsing of the JSON in more-expressive languages.

[mathisloge]

Hey, thanks for highlighting. I'll look into this tomorrow in more detail 👍

[mathisloge]

@dodohand I've added protodocOrder to each field. It will have the count index as the member vector in commsdsl (as specified in the schema xml.)