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

Issue with decoding when element is nullable array #305

Open
AndyBond2007 opened this issue May 6, 2022 · 0 comments
Open

Issue with decoding when element is nullable array #305

AndyBond2007 opened this issue May 6, 2022 · 0 comments

Comments

@AndyBond2007
Copy link

If you take the following array:

[ {"id": 1, "name" : "test", "tags" : ["tag1", "tag2"]}, {"id":2, "name":"test2", "tags":null}]

it fails on decode with the error:
Expected to decode Array but found a null value instead.

the "tags" element is correctly defined in the model as [String]? and the swagger document shows it is nullable.

It its possible to get around this by using the SafeOptionalDecoding:true option, but I would not have expected that to be required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant