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

Fix isNullish to not consider an empty string as Null. #228

Merged
merged 2 commits into from
Aug 5, 2017

Conversation

chris-ramon
Copy link
Member

Overview

Test plan

  • go test ./...

An empty string is still a perfectly valid string, in both situations:
(1) An empty string is a valid string argument to a handler.
(2) An empty string is a valid non-null result from a handler.

I also removed the unused and unnecessary PrivateName value from the
NonNull struct -- it served no purpose and screwed up tests when isNullish
was fixed.
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.005%) to 82.1% when pulling 2ddab1a on augustoroman/master into 1486d45 on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.005%) to 82.1% when pulling 2ddab1a on augustoroman/master into 1486d45 on master.

@chris-ramon chris-ramon merged commit a9df066 into master Aug 5, 2017
@chris-ramon chris-ramon deleted the augustoroman/master branch August 5, 2017 20: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.

3 participants