Revise approach to storing contract blocks order
Clarification and motivation
With #695 (closed) we will get an issue.
If I have a Michelson contract defined like
parameter ...
view ...
view ...
storage ...
code ...
view ...
the current approach of hardcoding all the possible variations of parameter
/storage
/... blocks just not going to work.
In #695 (closed) I'm planning to leave views so that they are always put in the end on parse-print roundtrip, their order is not preserved, and in this issue we should refactor the block order preservation and start preserving the order of views too.
Acceptance criteria
- Parse-print roundtrip and other roundtrips on
Contract
types do not lose the order of entries.
Edited by Konstantin Ivanov