You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Several of the protocol code generators use the Smithy HttpBindingIndex class to determine which members belong to which parts of the HTTP request/response. The HttpBindingIndex only returns meaningful information if there are @http traits in the Smithy model, so it doesn't work for all of the protocols, but it would simplify the XML codegen if we could generalize this functionality over its uses in both AwsQuery and RestXml, and it may also simplify the JSON generators.
The idea is to create a generalized HttpBindingResolver that can use HttpBindingIndex if there are @http traits, or fall back to some default logic if there aren't.
The text was updated successfully, but these errors were encountered:
Several of the protocol code generators use the Smithy
HttpBindingIndex
class to determine which members belong to which parts of the HTTP request/response. TheHttpBindingIndex
only returns meaningful information if there are@http
traits in the Smithy model, so it doesn't work for all of the protocols, but it would simplify the XML codegen if we could generalize this functionality over its uses in both AwsQuery and RestXml, and it may also simplify the JSON generators.The idea is to create a generalized
HttpBindingResolver
that can useHttpBindingIndex
if there are@http
traits, or fall back to some default logic if there aren't.The text was updated successfully, but these errors were encountered: