A override for a trait methods.

[allanmcarvalho]

Description

Sometimes we created a Trait that is used in a lot of class, or only use a trait of a dependency package. I believe that this is so common today at PHP modern projects.

But I see a big opportunity of improvement on this. Today, when we want to implement some code lines before or after a parent class method is very easy, we just to do:

protected function parentMethod(mixed $fooAttribute): mixed
{
    // do something here
    $result = parent::parentMethod($fooAttribute);
    // or do something here
    return $result;
}

I believe that a similar behavior will be very nice on traits, but I don't found a correspondent code to do this with it.

Maybe the right suggestion to do this is:

protected function traitMethod(mixed $fooAttribute): mixed
{
    // do something here
    $result = trait::traitMethod($fooAttribute);
    // or do something here
    return $result;
}

Make sense or it's a bad idea?

[damianwadley]

The problem is that traits aren't inheritance: they're copy and paste. Defining a method in a trait and then useing that trait in a class is very much like copying-and-pasting that method's code into your own class.

But it's easy to do what you want by aliasing the trait's method to a different name, then calling that method in your new implementation: https://3v4l.org/QiV28

[github-actions]

No feedback was provided. The issue is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so. Thank you.