Laravel 9 Mutator - Custom field

@MohamedTammam This not work for me. Just return empty.

That's my code:

    public function dataForHumans(): Attribute
    {
        $correctValue = $this->periodo == 'month'
            ? date('m/Y', strtotime($this->data))
            : date('d/m/Y', strtotime($this->data));

        return Attribute::make(get: fn($correctValue) => $correctValue);
    }

@patrickmaciel How are you calling it?

@MohamedTammam $model->dataForHumans

@patrickmaciel try: $model->data_for_humans

On the first example the docs says:

In this example, we'll define an accessor for the first_name attribute.

and then the example code below it defines a firstName(): Attribute method.

https://laravel.com/docs/9.x/eloquent-mutators#defining-an-accessor

Also the previous way of defining accessors/mutators also still work, but like the same you would define:

public function getDateForHumansAttribute()
{
    // accessor code here
}

And called it like:

$model->date_for_humans;

Note I preserved date_for_humans and date_for_humans according to each code sample you sent.

@patrickmaciel It should be

public function dataForHumans(): Attribute
{
        $correctValue = $this->periodo == 'month'
            ? date('m/Y', strtotime($this->data))
            : date('d/m/Y', strtotime($this->data));

        return Attribute::make(get: fn($value) => $correctValue);
}

But personally for this example I prefer the old way.

public function getDataForHumans()
{
        $correctValue = $this->periodo == 'month'
            ? date('m/Y', strtotime($this->data))
            : date('d/m/Y', strtotime($this->data));

        return $correctValue;
}

@rodrigo.pedra i wll try that.

Related to the old way to do that, I don't want to use that. I think if they provide a new way, I need to use that (as a good practice).

@patrickmaciel you are sure right.

The previous way is not even documented anymore. But sometimes is good to know when working on legacy projects