@matheusd brought up the strange lack of "required" parity between ConstructionPreprocessResponse.Options and ConstructionMetadataRequest.Options in https://github.com/coinbase/rosetta-sdk-go/pull/166. This was originally intended so the caller to opt to avoid calling /construction/metadata if there were no ConstructionPreprocessResponse.Options.
As a result of the conversation on that PR, we've decided it is best to not make Options required in ConstructionMetadataRequest in the case that an implementer does not need to pass any info related to the /construction/preprocess execution. As a side note, this means we can remove the conditional nature of the Construction API flow.
@matheusd brought up the strange lack of "required" parity between
ConstructionPreprocessResponse.Options
andConstructionMetadataRequest.Options
in https://github.com/coinbase/rosetta-sdk-go/pull/166. This was originally intended so the caller to opt to avoid calling/construction/metadata
if there were noConstructionPreprocessResponse.Options
.As a result of the conversation on that PR, we've decided it is best to not make
Options
required inConstructionMetadataRequest
in the case that an implementer does not need to pass any info related to the/construction/preprocess
execution. As a side note, this means we can remove the conditional nature of theConstruction API
flow.Changes
Options
requirement