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

Improve clarity for treating null for List values #213

Merged
merged 1 commit into from
Sep 19, 2016
Merged

Conversation

leebyron
Copy link
Collaborator

As mentioned in #83, we had left the treatment of input null by a List value ambiguous, while there is an intended behavior.

Because of the existing language, it's easy to misinterpret providing null to [String] as the value [null], while the correct interpretating would be null.

As mentioned in #83, we had left the treatment of input `null` by a List value ambiguous, while there is an intended behavior.

Because of the existing language, it's easy to misinterpret providing `null` to `[String]` as the value `[null]`, while the correct interpretating would be `null`.
leebyron added a commit that referenced this pull request Sep 19, 2016
As mentioned in #83, we had left the treatment of input `null` by a List value ambiguous, while there is an intended behavior.

Because of the existing language, it's easy to misinterpret providing `null` to `[String]` as the value `[null]`, while the correct interpretating would be `null`.
@leebyron leebyron merged commit 910b694 into master Sep 19, 2016
@leebyron leebyron deleted the list-null branch September 19, 2016 17:45
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.

None yet

2 participants