[5.8] Added Tappable trait

[pascalbaljet]

A little helper trait to add the tap function to any class and remove the need for temporary variables. I've used it in the case where doSomething and doSomethingElse don't return the instance :)

$result = TappableClass::make()->tap(function ($tappable) {
    $tappable->doSomething();
    $tappable->doSomethingElse();
})->getResult();

[driesvints]

I feel this is unnecessary to add this to the core framework and something you can just use in your own codebase if you want to.

[seriquynh]

You can publish this trait to a package.

[deleugpn]

Isn't that the same as tap(YourClass::make())->...()?

[devcircus]

I don't see what this would've solved but I may be overlooking something.

[pascalbaljet]

I don't see what this would've solved but I may be overlooking something.

The doSomething and doSomethingElse methods don't return the TappableClass instance itself, so to call these methods and then call the getResult method, you need a temporary variable.

// without tap
$tappable = TappableClass::make();
$tappable->doSomething();
$tappable->doSomethingElse();
$result = $tappable->getResult();

// with tap method
$result = tap(TappableClass::make(), function ($tappable) {
    $tappable->doSomething();
    $tappable->doSomethingElse();
})->getResult();

// with Tappable trait
$result = TappableClass::make()->tap(function ($tappable) {
    $tappable->doSomething();
    $tappable->doSomethingElse();
})->getResult();

I prefer to call the tap method on an instance over calling the global helper. For example with the Collection class, I think $collection->tap() is much cleaner than tap($collection) but this a personal preference of course. I've used this new Tappable trait on a project and really liked it so I though more fans of tap would like to see this added to illuminate/support ✌️

[taylorotwell]

I can't resist this. ❤️

[devcircus]

@pascalbaljet would you mind sending a PR to the docs to explain this?

[pascalbaljet]

@devcircus yes!

[devcircus]

Not sure exactly where the best place for this would be in the docs but otherwise it would mostly go unnoticed in the framework.