Skip to content
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

fix(clients): parse status code bindings in rest protocols #2483

Merged
merged 1 commit into from
Jun 15, 2021

Conversation

AllanZhengYP
Copy link
Contributor

Resolves #2021
Related to smithy-lang/smithy-typescript#354

Description

parse the status code traits for rest protocols.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@codecov-commenter
Copy link

Codecov Report

❗ No coverage uploaded for pull request base (main@3bd30bb). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #2483   +/-   ##
=======================================
  Coverage        ?   59.54%           
=======================================
  Files           ?      493           
  Lines           ?    26359           
  Branches        ?     6262           
=======================================
  Hits            ?    15695           
  Misses          ?    10664           
  Partials        ?        0           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3bd30bb...bd6f171. Read the comment docs.

@AllanZhengYP AllanZhengYP merged commit 6d4e6b5 into aws:main Jun 15, 2021
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

LambdaClient InvokeCommand response is missing StatusCode
3 participants