public function andWhereNot($field, $value)
{
return call_user_func_array([$this, 'whereNot'], func_get_args());
}
has been used instead of
public function andWhereNot($field, $value)
{
return $this->whereNot($field, $value);
}
which would have been, imho, way more explicit and readable. Is there any particular reason? I'd be willing to refactor all the call_userfunc* usage to direct method calls (of course when it make sense) if you guys will accept a PR for this.
I'm having hard time figuring out why this
has been used instead of
which would have been, imho, way more explicit and readable. Is there any particular reason? I'd be willing to refactor all the call_userfunc* usage to direct method calls (of course when it make sense) if you guys will accept a PR for this.