This issue proposes to remove the version field on the transaction model since the version of the transaction model is currently tightly coupled to that of the server, and the server cannot process different schema versions.
Or perhaps, put in the form of a question: "Could we simplify the transaction payload by removing the version for now since it is tightly coupled to the server version, and the server does not currently handle multiple schema versions?"
Although arguably minimally, this could help in simplifying client code that generate payloads, and would also simplify server code.
This issue proposes to remove the
version
field on the transaction model since the version of the transaction model is currently tightly coupled to that of the server, and the server cannot process different schema versions.Or perhaps, put in the form of a question: "Could we simplify the transaction payload by removing the version for now since it is tightly coupled to the server version, and the server does not currently handle multiple schema versions?"
Although arguably minimally, this could help in simplifying client code that generate payloads, and would also simplify server code.