-
Notifications
You must be signed in to change notification settings - Fork 578
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
feat: add default destroy function to clients #1081
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1081 +/- ##
===========================================
- Coverage 91.49% 78.79% -12.70%
===========================================
Files 146 279 +133
Lines 2868 11598 +8730
Branches 511 2402 +1891
===========================================
+ Hits 2624 9139 +6515
- Misses 244 2459 +2215
Continue to review full report at Codecov.
|
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
CodeGen needs to be run post this update in dependent package smithy-lang/smithy-typescript@1e11300 |
@trivikr Thanks for the heads up. In fact no diff will be generated from the commit |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread. |
Currently all the clientRuntimeCustomization can have a
destroy()
function. But the default configs in smithy client doesn't have one:aws-sdk-js-v3/packages/smithy-client/src/client.ts
Line 27 in 77386f6
This change adds a
destroy
function to the Smithy client. When every service client extends the Smithy client, it has a defaultdestroy
function. In the service clients'destroy
function, it will call the function from its super class Smithy client. This is necessary as you can destroy the Smithy resolved config just like destroying other client customization.The last commit is client generation diff. You can ignore it when reviewing it.
Related: smithy-lang/smithy-typescript#156
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.