Default encoder now excludes Option.None instead of "key":null #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Looks good to me |
jeremyrsmith
added a commit
that referenced
this pull request
Mar 10, 2016
Default encoder now excludes Option.None instead of "key":null
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default, when JSON-encoding case classes, circe encodes Options like
case class MyClass(one:String, two:Option[String]); MyClass("myval", None)as{ "one":"myval", "two":null }Now, by default featherbed will encode it as
{ "one":"myval" }and exclude the None. This makes more sense for a JSON API client, where Option case class values probably represent optional API keys.