Is it correct to use get/set and other methods in the model of the Laravel?

Question

Example:

In the model:

public function getProduct()
{
  return $this->where('price',100)->get();
}

public function checkProduct($price)
{
  if($price > 100){
     return $price;
  }
}

On the controller:

$product = new Product();
$product->getProduct();
$product->checkProduct();

Answer 1

is not incorrect, but there are ways that the eloquent itself delivers:

• your first example getPoduto should have a better context of name maybe (I’m imagining you’re using the "Product" model) ... say by Pro and then use a Scope in your model:

public function peloPrecoScope($query, $preco = 100) {
   return $query->where('preco', 100);
}

This way you’d wear it like this:

$produto = Produto->peloPreco(200)->first(); // ou get - aqui estou pegando o primeiro registro apenas do retorno

And yes, the check would probably be as you specified.

See nothing prevents you to use as described, often I have situations where I need the return to be "hard" (hard coded) with a get method, but often implement the filter option in the model using Scopes is the output that delivers more reuse of code and better reading comprehension of it.

To better understand the Copes see in the documentation: Eloquent - Query Scopes