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
When/WhenNot methods for db in a trait #6574
When/WhenNot methods for db in a trait #6574
Changes from all commits
dd1b474
adcf538
e12932e
b29f2d1
b0a1bea
3ba4e1f
fc3d16a
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.
whenNot
as the inverse ofwhen
seems quite not natural for me. It's a bit off. How about other antonyms ofwhen
: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 method expects the condition to evaluate to
false
, which makesexcept
andunless
not make semantic sense.ifNot
as an opposite ofwhen
feels wrong also.lest
feels like the condition should evaluate totrue
to me, also.whenNot
does at least match the pattern of other methods likewhere
/whereNot
. I'm open to suggestions but I'm not sure any of these fit, unless we change the whole method to suit the name.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.
except
/unless
makes sense to me if the statement is read in a specific way. In the context of the DB builder, since I know the usage ofwhen
then when I read its inverse (except
/unless
):In this example, I would read the code as "Except when
$user
is truthy (or a found user record), let the$builder
execute the callable then get the DB result."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.
whenNot
is easy to understand for non native English speakers.It is logical. The
when
whenNot
pair is easy to remember, because we already have where/whereNot.except
is difficult to imagine as the opposite ofwhen
.