[8.x] Use "Conditionable" in existing classes that implement when() #37561
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.
Right now,
BuildsQueries
,Mailable
,MailMessage
, andStringable
all implement their own version ofwhen()
that is exactly the same as the implementation in the newConditionable
trait. This PR just swaps them out for the new trait instead.(This means that
Mailable
gets anunless()
method as well. All other classes had both awhen()
andunless()
method already.)It's also worth noting that
unless()
was implemented in two different ways in the framework. One implementation was a mirror of thewhen()
implementation, while another approach was to call$this->when(! $value, ...)
. It turns out that the latter solution (callingwhen()
) is incorrect, because it ends up passing the result of! $value
to the callback, rather than the actual value. This PR fixes that issue in theConditionable
trait, thus standardizing it across all the classes that use it.