Suggest brew update && … when handling errors or missing methods

[claui]

As @ndr-qef and @rolandwalker suggested on IRC.

This is supposed to help cut trivial issues that would be easily fixable by doing brew update && … etc.
Also, splitting unit tests in two to keep one from triggering the other.

[claui]

Generic error

Warning: missing method

[rolandwalker]

my only question is what this empty #{} does

[claui]

I’ve been taught that lines longer than 80 chars are bad.
Sometimes this makes me feel so guilty that I even try to follow this rule in herestrings. 😊

Am I free to ignore this rule in herestrings? Or maybe you happen to know a less confusing way to soft-wrap long lines?

[rolandwalker]

Then it is a clever trick.

You are free to do as you please, in heredocs and elsewhere. We can adopt a style re: wrapping across the codebase if it benefits you. I tend to let code run wide, which attracts criticism.

[claui]

Thanks for reviewing and for the comments!

Oh, I’m fine with the codebase as it stands. Should we ever commit to any stylistic rules (as the number of backend devs – hopefully – grows with the project), I’ll be happy to adhere to them!

[vitorgalvao]

Great news to have this implemented. This also likely means I’ll be able to retire one of my TextExpander snippets.

However, is

still the final message?

“Oh no, I accidentally the whole Caskroom” makes no sense.

[tapeinosyne]

It is merely a placeholder used in the screenshot.

[vitorgalvao]

Ah, good. I couldn’t find it in the PR itself, so I was wondering if it was there from before.

[claui]

@ndr-qef You’re correct, thanks for clarifying 😊

@vitorgalvao I temporarily placed a fail command in Cask::CLI::List::run which was the only way to provoke an error I could come up with on the spot. I faintly remember that I have come across an internal CLI command at some point in the past that was specifically drafted for this. I looked for it yesterday, but I’ve got no idea where it is 🙈