Luc Talatinian
Luc Talatinian
Tracked by #458 - the json family of protocol generators should handle this.
I'm going to close this - this should be handled via protocol generation, specifically we'll get json protocol support (including `jsonName`) by addressing #458.
I would note that smithy-go now supports modeled endpoint resolution, though the feature isn't part of the public IDL docs. That aside I have #458 open to track making smithy-go...
This is true for every aws protocol right now, moving to #458.
Covered by #458, protocol serde should handle this.
On its own smithy-go isn't usable its in current state - we need to at the very least move the protocol generators out of the SDK into this project (#458)....
> I don't think the middleware solution is graceful enough for us since it changes the behavior for all requests using that client. That's not the case in [@RanVaknin's example](https://github.com/aws/aws-sdk-go-v2/issues/1862#issuecomment-1279693213)...
Aside, this can be done without having to deal with middleware injection - remember the client itself is an input to the waiter, we can just wrap one to enforce...