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
This is a tracking issue for implementing schema objects and associated features.
Since schemas are an implementation detail that is not relevant to the typical generated-client consumer, I won't go into a long explanation of what they do. They are instruction objects for request serialization and response deserialization.
Going along with this change, two features are planned:
protocol selection can be done at runtime for clients, enabling different communication formats with services supporting more than one protocol without needing to generate separate clients.
BigDecimal and BigInteger support for all protocols and formats.
Uh oh!
There was an error while loading. Please reload this page.
This is a tracking issue for implementing schema objects and associated features.
Since schemas are an implementation detail that is not relevant to the typical generated-client consumer, I won't go into a long explanation of what they do. They are instruction objects for request serialization and response deserialization.
Going along with this change, two features are planned:
PRs
PoC branch - #1592
#1593 - schema types
#1594 - migrate serde functions
#1595 - schema runtime classes
#1599 - java codegen
#1603 - BigInt and BigDecimal support in CBOR codec
AWS SDK for JavaScript (downstream consumer)
PoC branch - aws/aws-sdk-js-v3#6986
aws/aws-sdk-js-v3#7110 - protocol runtime classes
aws/aws-sdk-js-v3#7109 - (chore) import core submodules instead of index
The text was updated successfully, but these errors were encountered: