Traits — Horizontal Reuse (PHP 5.4)

TL;DR

Explanation

Traits (PHP 5.4) allow including method groups in multiple classes: trait Timestampable { public function touch(): void { $this->updatedAt = new DateTime(); } }. Multiple traits per class with use Trait1, Trait2. Conflict resolution: insteadof and as operators. Traits can define abstract methods (requiring implementing class to provide them), properties, and constants (PHP 8.2). Downsides: traits create implicit coupling, make code harder to test (no mock boundary), and can lead to 'trait soup'. Prefer composition (inject a collaborator) when the trait becomes large or complex.

Common Misconception

Why It Matters

Common Mistakes

• Overusing traits as a workaround for lack of multiple inheritance — prefer composition.
• Traits that depend on specific properties of the host class — tight implicit coupling.
• Not resolving trait conflicts explicitly when using multiple traits with same method names.

Code Examples

// Trait depending on host class internals — implicit coupling:
trait Logger {
    public function log(): void {
        // Assumes $this->name exists in host class
        echo $this->name . ' logged';
    }
}

trait Timestampable {
    private ?DateTime $updatedAt = null;

    public function touch(): void {
        $this->updatedAt = new DateTime();
    }

    public function getUpdatedAt(): ?DateTime {
        return $this->updatedAt;
    }
}

References

• ↗ https://www.php.net/manual/en/language.oop5.traits.php

Tags

Related Terms