Skip to content

added config option to scalar type to allow the serialize to return null#1066

Closed
bradzacher wants to merge 1 commit intographql:masterfrom
bradzacher:1057-allow-null-serialize
Closed

added config option to scalar type to allow the serialize to return null#1066
bradzacher wants to merge 1 commit intographql:masterfrom
bradzacher:1057-allow-null-serialize

Conversation

@bradzacher
Copy link
Copy Markdown

as per #1057.

@leebyron
Copy link
Copy Markdown
Contributor

leebyron commented Dec 1, 2017

Thanks for your work on this.

I'd like to avoid changing behavior via configuration flags in favor of improved behavior overall. I'll put up a PR to solve the original issue

leebyron added a commit that referenced this pull request Dec 1, 2017
This changes the check for null/undefined to a check for undefined to determine if scalar serialization was successful or not, allowing `null` to be returned from serialize() without indicating error.

This is potentially breaking for any existing custom scalar which returned `null` from `serialize()` to indicate failure. To account for this change, it should either throw an error or return `undefined`.

Fixes #1057
Closes #1066
leebyron added a commit that referenced this pull request Dec 1, 2017
This changes the check for null/undefined to a check for undefined to determine if scalar serialization was successful or not, allowing `null` to be returned from serialize() without indicating error.

This is potentially breaking for any existing custom scalar which returned `null` from `serialize()` to indicate failure. To account for this change, it should either throw an error or return `undefined`.

Fixes #1057
Closes #1066
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants