Hey there 👋🏻 , as somebody passionate about the topic and with way too many scars I wish to have, I would like to be able to decide how the return payload is returned:
I may return the data as a map, struct, or without decoding as string/raw.
-
map because you do not want the double-pass of decoders, and speed is critical. Also, primitive obsessions are helpful when taking advantage of derives out there.
-
struct, you are ok with the double-pass and want to work with structs.
-
raw when you want to pass the data to another service without doing much (I have seen this a lot with Stripe)
Related to beam-community/stripity-stripe#805
Hey there 👋🏻 , as somebody passionate about the topic and with way too many scars I wish to have, I would like to be able to decide how the return payload is returned:
I may return the data as a
map,struct,or without decoding asstring/raw.mapbecause you do not want the double-pass of decoders, and speed is critical. Also, primitive obsessions are helpful when taking advantage of derives out there.struct,you are ok with the double-pass and want to work with structs.rawwhen you want to pass the data to another service without doing much (I have seen this a lot with Stripe)Related to beam-community/stripity-stripe#805