Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Jun 6, 2017

…e items in an array in a REST response fixes #398

…e items in an array in a REST response fixes #398
@pivotal-issuemaster
Copy link

@nakulcg Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@pivotal-issuemaster
Copy link

@nakulcg Thank you for signing the Contributor License Agreement!

@wilkinsona
Copy link
Member

Thanks for the PR. Did you intend to undo the commit that proposed a fix for the problem?

@ghost
Copy link
Author

ghost commented Jun 9, 2017

Yes. Because I think it might introduce other problems. Because it then renders the JsonFieldType.NULL useless.

@wilkinsona
Copy link
Member

Got you, thanks. Yeah, your test actually reveals another problem which is that it should fail because you haven't marked assets[].name as optional yet it isn't always there. I've opened #402 for that.

@wilkinsona
Copy link
Member

Thanks for the PR, @nakulcg

@wilkinsona wilkinsona changed the title Dont enforce varies type on field which might have null in some of th… Add a test that shows problem with sometimes null field within an array Jul 1, 2017
@wilkinsona wilkinsona added this to the 1.2.2.RELEASE milestone Jul 1, 2017
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

Successfully merging this pull request may close these issues.

Field beneath an array that is sometimes null cannot have a type other than varies

2 participants