suggestion: allow to set ButtonComponent as OptionalButton

[onebeastchris]

Currently, a new button can be added with .button(ButtonComponent button), or with a string (and optional FormImage). It would be nice if there was a way that an .optionalButton could accept an existing button component + boolean; similar to how .button works

that'd be neat

thanks!

[Tim203]

Is there an actual use case for creating this method overload?

I've been thinking about having more lambda options, e.g.:

.optionalButton(true /* shouldAdd */, builder -> { /* button builder */ })

For SimpleForms and

.stepSlider(builder -> { /* step slider builder */ })

For CustomForms.
Back in the day when Cumulus 1.0 was being designed, I was going very heavy on builders methods like:

.stepSlider(StepSliderBuilder.text("hi").step("hello"))

But because a lot of formatters did not format this well for more complex situations (and you honestly can't always do everything on one line), its design eventually went more in the method overload direction.
However lambdas allow multiline, have minimal overhead these days, and would be added in addition to the existing methods.

The reason why I'm mentioning this is because I can see the usefulness of having an optional parameter here (see also my example, I included it there). You could use that boolean shouldAdd to determine if you want to add that button, and only if you want to have it the lambda will run.
But with the method you suggested, you should already know if you want to add that button, because why otherwise would you create that button instance?