Allow describe without requiring an argument

[straight-shoota]

The describe method of the spec DSL currently requires an argument for the description. The general idea behind that is probably, that it makes no sense to describe something without a description.

With spec's focus feature I've several times found myself in a situation where I want to run a couple of related examples in a spec file. Adding focus: true on each one is cumbersome, so I created a (temporary) example group with describe and added focus: true to that. But describe requires an argument with a description. For this focus-only example group I don't need a description, so could just be empty.

I'm proposing to add a default value to the description argument, to make this use case a bit friendlier. Now I'm no longer forced to pass in an empty description.

context is functionally identical to describe, so it also gets a default argument.

[asterite]

Hm, it seems that works in RSpec too 🤷

Approved! 😄

[Fryguy]

Can a spec be added for this case? I can't look at the rest of the code at the moment, but I'm concerned that it will create deep description strings with "bonus" whitespace inside.

[straight-shoota]

There are currently no specs for spec output. Adding that is a different topic (see #5671 for example).

And yes, this will probably add extra whitespace into spec descriptions. But that's a also a different issue. This behaviour is not introduced by this PR, it's already that way if I use describe nil {} or describe "" {} explicitly.