Use traits instead.

[etrepat]

Use traits instead.

[etrepat]

I understand the benefits of composition over inheritance where they're applicable.

The main problem I have with coding Baum as a trait or with a collection of traits is PHP 5.3.x compatibility. If Laravel/Eloquent are compatible with PHP 5.3.x so should be a package designed for them.

If your object model is not too complex though, I don't see why you couldn't extend Baum (as you'd probably have extended Model with Eloquent anyway) and "compose/mix" in your business logic with traits.

[atrauzzi]

That's probably not the best assumption to make as you're not the first library I've recommended switch to traits that has had this response.

So, in theory, each library is now competing to be the "base class". Can't be all of them, so which will it be?

Also, FWIW, PHP 5.3 is EoL, not much point in worrying about it anymore. All in all, seems like a losing battle.

[etrepat]

I understood your point.

There's no "one size fits all" solution to this. So I'm making a compromise here for the sake of being as close to Eloquent's requirements as possible, at least right now.

There's some important features I'd like to have implemented before moving the requirements forward. Thanks for the suggestion, though.

[deanmraz]

@etrepat can you revisit this request?

Laravel 4.2 is using traits for Eloquent's soft deleting feature: http://laravel.com/docs/4.2/eloquent#soft-deleting

[jcwatson11]

+1 for revisiting this issue. Converting to a trait would allow a lot more flexibility for all.