Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore(codegen): sync for handling empty structure payloads #7199

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

Draft
smilkuri wants to merge 1 commit into main
base: main
Choose a base branch
Loading
from restJsonPt

Conversation

@smilkuri
Copy link
Contributor

@smilkuri smilkuri commented Jul 11, 2025
edited
Loading

Issue

#7169

Description

What does this implement/fix? Explain your changes.

Testing

dev-dsk-smilkuri-1a-17aece6b % yarn lerna run test --scope '@aws-sdk/aws-protocoltests-restjson'
lerna notice cli v5.5.2
lerna notice filter including "@aws-sdk/aws-protocoltests-restjson"
lerna info filter [ '@aws-sdk/aws-protocoltests-restjson' ]
lerna info Executing command in 1 package: "yarn run test"
lerna info run Ran npm script 'test' in '@aws-sdk/aws-protocoltests-restjson' in 6.3s:
 RUN v2.1.9 /local/home/smilkuri/aws-sdk-js-v3/private/aws-protocoltests-restjson
 ✓ test/functional/restjson1.spec.ts (240 tests | 10 skipped) 1893ms
 Test Files 1 passed (1)
 Tests 230 passed | 10 skipped (240)
 Start at 15:53:56
 Duration 3.52s (transform 879ms, setup 0ms, collect 1.34s, tests 1.89s, environment 0ms, prepare 96ms)
lerna success run Ran npm script 'test' in 1 package in 6.3s:
lerna success - @aws-sdk/aws-protocoltests-restjson
  • Yet to fix the failing test RestJsonHttpPayloadWithStructureAndEmptyResponseBody:Response in @aws-protocoltests-restjson-schema

Additional context

Add any other context about the PR here.

Checklist

  • If you wrote E2E tests, are they resilient to concurrent I/O?
  • If adding new public functions, did you add the @public tag and enable doc generation on the package?

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

AltStyle によって変換されたページ (->オリジナル) /