Use @smithy scoped packages #766
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pose
approved these changes
May 15, 2023
kuhe
approved these changes
May 15, 2023
srchase
force-pushed
the
use-smithy-types-protocol-http
branch
2 times, most recently
from
ef77fc5
to
1885b31
Compare
srchase
force-pushed
the
use-smithy-types-protocol-http
branch
from
1885b31
to
51925de
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the generated code to use the
@smithyscopedtypesandprotocol-httppackages that were added to the/packagesdirectory. For now, generated clients will continue to depend on@aws-sdk/typespackage, but@aws-sdk/protocol-httpis completely replaced by the package migrated to@smithy/protocol-https.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.