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

feat(codegen): reject null in non-sparse collections #2771

Merged
merged 1 commit into from
Sep 9, 2021

Conversation

JordonPhillips
Copy link
Member

Issue

n/a

Description

This updates list parsing for SSDKs to throw an error whenever a
null value shows up in a list or set that isn't meant to be sparse.

Clients remain tolerant of these nulls to preserve compatibility with
services that are not so strict.

Testing

Tests from main on smithy were run.

Additional context

n/a


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-commenter commented Sep 9, 2021

Codecov Report

Merging #2771 (ae09d4b) into main (aa62fc3) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #2771   +/-   ##
=======================================
  Coverage   60.15%   60.15%           
=======================================
  Files         548      548           
  Lines       28586    28586           
  Branches     6997     6997           
=======================================
  Hits        17196    17196           
  Misses      11390    11390           

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 aa62fc3...ae09d4b. Read the comment docs.

This updates list parsing for SSDKs to throw an error whenever a
null value shows up in a list or set that isn't meant to be sparse.

Clients remain tolerant of these nulls to preserve compatibility with
services that are not so strict.
@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 Sep 24, 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.

None yet

3 participants