chore: use bare-bones and aggregated instead of modular/non-modular #457
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
This was referenced Oct 24, 2021
Merged
AllanZhengYP
approved these changes
Oct 25, 2021
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.
Issue #, if available:
Refs: aws/aws-sdk-js-v3#2205
Description of changes:
In March 2021, the AWS SDK for JavaScript team had decided to use bare-bones/aggregated instead of modular/non-modular for clients to avoid confusion. This change was done in aws-sdk-js-v3, but not in smithy-ts side.
This PR updates:
ServiceGeneratortoServiceBareBonesClientGeneratorNonModularServiceGeneratortoServiceAggregateClientGeneratornonModular*toaggregated*By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.