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.
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
Refactor informal taxon groups usage according to api changes #701
Refactor informal taxon groups usage according to api changes #701
Changes from 5 commits
b59eebd
b997423
92d9bbe
136d433
82ba0ef
e565ed0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't it be
removeNullableFields
or at leastwithNoNullableKeys
? This name sounds to me like you are adding extra keys rather than removing nullable keysThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
another alternative:
getNonNullableKeys
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The term
NonNullable
comes from TypeScript: NonNullableThough the "keys" word usage is weird... How about
withNonNullableValues
?getNonNullableKeys
sounds to me like it would return keys of an object.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I pushed
withNonNullableValues
as a proposal. Updated the JS doc comment also. It was copy pasted from some other utility fn so there was an extra param.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still don't think I would immediately understand what
withNonNullableValues
does without reading the comment. Usually the wordwith
I would associate with adding something to the result, eg.withLatestFrom
in rxjs. MaybeexcludeNullables
or invert itselectNonNullables
.Sorry this is getting rather pedantic... I'll give the PR an approve.