Samuel Williams

I agree. There is also the implicit performance costs associated with wrapping everything, e.g. a memory allocation, a method call to get the actual value, etc. It might also mean...

Everything here is very reasonable and well thought out. I agree with all of it. However, I still think the original issue should be solved in a way which doesn't...

If you wanted a rule, perhaps this is it: For methods that return "composite" objects, e.g. arrays, dictionaries, dates, objects, the object can be chained. But for simple values, e.g....

I'm pretty sure 99% of use cases of `isValid()` is going to be `if (date.isValid())`.

So you propose to make all `isFoo` methods return unwrapped boolean? I think it's a good idea.

(1) Nope, but both are acceptable. I started with `@param` because it's common. However after creating https://github.com/ioquatix/decode I realised I wanted to avoid abbreviations so reworked this to use `@parameter`....

For (3), maybe we can introduce `bake --gem my_gem command ...` This would execute `gem "my_gem"` before trying to run the command and also allow for version selection, e.g. ```...

I'm less concerned about "general users" and more concerned about my own use cases. Personally, If I can do away with CLIs provided by gems and just use bake, I'd...

I added experimental support for loading gems. https://github.com/ioquatix/bake/commit/e7f97175df203a4bda3712715356c68512d9d73b

cc @olleolleolle & @picatz FYI :)