-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Epic: Make smithy-swift a stand alone product #186
Labels
feature-request
A feature should be added or improved.
Comments
kneekey23
changed the title
Move xml, json, ec2, aws query classes to smithy-swift
Move xml, json, ec2, aws query classes to aws-sdk-swift
Aug 23, 2021
Moved aws query over here: |
wooj2
changed the title
Move xml, json, ec2, aws query classes to aws-sdk-swift
Epic: Make smithy-swift a stand alone product
Sep 24, 2021
ganeshnj
added
feature-request
A feature should be added or improved.
needs-triage
This issue or PR still needs to be triaged.
and removed
feature
labels
Oct 4, 2022
Closing this ticket now because concrete work defined for moving AWS protocol things to aws-sdk-swift is complete, and because making smithy-swift a standalone project will be revisited based on customer demand. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description located here:
smithy-lang/smithy-swift#243 (comment)
By making smithy-swift a stand alone product, the following classes need to get moved over:
xml, json, ec2, aws query classes to aws-sdk-swift
(however, -- i suspect there are more classes that also need to get moved over)
internal id: 178442037
The text was updated successfully, but these errors were encountered: