Replies: 2 comments 1 reply
-
Some of the protobuf structures certainly are very complex -- maybe overly complex -- particularly where there are multiple nested layers of serialized protobuf messages. Unfortunately this is now a difficult thing to change. For reference, there are similar mock messages generated in Go, Node and Java unit tests:
|
Beta Was this translation helpful? Give feedback.
-
Thanks for pointing that out. The 12 indents 8 spaces per tab of the go test makes me want to cry. 😅 😂 |
Beta Was this translation helpful? Give feedback.
-
The prepared transaction is extremely complex. The fact that many of the objects are serialized instead of embedded directly makes it hard to trace down the hierarchy without having to refer to the protos constantly. I had to create my own mocked prepared transaction messages for testing, thought I'd leave this here if anyone found them useful. Unfortunately, it is in ruby, but it shouldn't be too hard to convert it to your language of choice.
Beta Was this translation helpful? Give feedback.
All reactions