feat(option): new Option::apply() method

[devnix]

I guess it's not an important method because you can return the same value with map, but I'll leave the proposal 😄

[coveralls]

Pull Request Test Coverage Report for Build 7355771608

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 99.012%

---

Totals
Change from base Build 7354836553:	0.0%
Covered Lines:	4211
Relevant Lines:	4253

---

💛 - Coveralls

[veewee]

What would be the big benifit of this over using map()?
Would you consume it and chain it back into doing another operation?

I don't see how I'dd use it personally at this moment, but I'm open for opinions :)

[devnix]

Just syntactic sugar for operations if it holds some, but avoiding worrying about the verbosity of returning the same value if you want to chain methods.

Code like this (probably not the best example)

$stock
    ->map(function (int $value) use ($logger) {
        $logger->info('New stock requested', ['stock' => $value]);
        return $value;
    })
    ->map(Stock::create(...))
    ->map(function (Stock $value) use ($product) {
        $product->updateStock($value);
        return $value;
    });

could be much more readable, and probably more expressive about intention:

$stock
    ->apply(fn (int $value) => $logger->info('New stock requested', ['stock' => $value]))
    ->map(Stock::create(...))
    ->apply(fn (Stock $value) => $product->updateStock($stock));

[veewee]

@devnix can you rebase against the next branch to get the github actions green again and add some tests?
It could make sense for people to have this option.

[veewee]

Looks good thanks. I've added a small couple of nitpicks to the code review.
After those it should be good to go!

[devnix]

@veewee I think this should be ready too, conflicts are resolved

[veewee]

Cool, Thanks again!