Feat (checkbox): Support validate config

[Srenky]

Second part of #1257

Added two new optional properties to config: minChoices, maxChoices

With these properties, users can specify how many choices can be selected.

The validation logic has been expanded.

Possible topic for discussion

• case when the user wants an exact number of choices selected, one possible option would be to make minChoices and maxChoices equal and extend validation logic with one more condition and its own message
• is this something to think about?

[SBoudrias]

Hey @Srenky, thanks for sending this PR!

I'll have to disagree on the approach taken unfortunately. Adding required felt like a very common use case, but limiting the selection amount feels like less so and I would prefer not to introduce a specific validation logic for it.

Instead, I'd prefer adding a generic validate config that can be used to implement any custom validation a user might need (prevent selection of conflicting choices, or just like you did, add validation for min/max selections, etc.)

You can see an example of a generic validate function in the input & editor prompts.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Files	Coverage Δ
packages/checkbox/src/index.mts	100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

📢 Thoughts on this report? Let us know!

[Srenky]

@SBoudrias Totally agree with you on this one. I didn't even think about using validate, but it does make sense to do it this way.

[SBoudrias]

Few comments, but overall this look solid! Thanks!

[SBoudrias]

Thanks a ton for the PR! Great addition :)