$builder->has('users', '=', static::MAX_MEMBERS) $builder->where('ranking', '>', $team->ranking) Public function scopeWhereRankedHigherThan($builder, $team) $this->scopeWherePublic($builder, false)
Public function scopeWherePrivate($builder) $builder->where('is_public', '=', $boolean) Public function scopeWherePublic($builder, $boolean = true) In reality I would not apply the refactor to this actual model until it was substantially bigger, but we can all use our imagination to pretend we have a bunch more stuff on this model.
MOCK ELOQUENT FIND METHOD HOW TO
We are going to use the following model as a starting point to show how to refactor out query scope methods to a dedicated query builder. It also does not change the public facing API for how you access / interact with your eloquent queries! But enough prologue, let's look some code.
Static analysis is able to understand your scopes (because we are removing the magic behind them). The ability to click through to method definitions for query scopes (because we are removing the "scope" prefix). Because scopes are an indirect way of extending the eloquent builder on a per class basis, extending the actual query builder on a per class basis just feels right to me.Ī couple of ancillary benefits also arise from introducing this pattern, including: If your models get larger than you would prefer, I feel that this is the natural place for scopes to be relocated to. The goal here is to thin models by moving query scope methods from the model to a dedicated query builder class, on a per model basis. The model is the perfect place for these things initially, but at a point I personally find I want the ability to thin out my models. As your application grows, more than likely your models will also grow as you add more attribute mutators, new relationships, additional query scopes, and other functionality. One of those conveniences is the co-location of eloquent attributes, relationships, and scopes on the model class. Out of the box Laravel comes with a long list of conveniences and scaffolding that help developers build out web applications quickly and efficiently. You can probably get everything you need from the tweet and the comments on it, but I've written this to make it Google-able if ever needed, and to cover some caveats you should be aware of. 
This blog post is an in-depth walk though of a tweet I sent out a few weeks ago.
0 kommentar(er)
