Use encodeIfPresent instead of custom helper function #70
Conversation
This file contains hidden or 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
siemensikkema
changed the title
mattpolzin
approved these changes
May 14, 2020
There was a problem hiding this comment.
wow. I'm a little bit shocked I never noticed that encodeIfPresent() existed in all the time I was using encodeIfNotNil().
Nice to get rid of a superfluous utility function and doubly nice to bring the property name and the coding key closer together in the source code (horizontal reading distance). 👍
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Encodable+EncodeIfNotNilwith the equivalent and built inEncoder.encodeIfPresent.CodableimplementationsOptional(made possible with the help of Xcode multiline editing 😅)