Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Enhancement] Templated CheckBox

See original GitHub issue

Summary

CheckBox should have a “Content” property similar to RadioButton. This property should allow you to set a string or a view.

Similar to #11628 and #7299 (this one seems to have been forgotten about).

API Changes

<CheckBox Content="I agree to the terms of service" />

Intended Use Case

The majority of use cases of a checkbox involve a label beside it that is clickable. To keep things consistent, the checkbox API should be similar to the existing RadioButton where you can have a template view instead of just a string.

Issue Analytics

State:
Created 2 years ago
Reactions:4
Comments:5 (1 by maintainers)

Top GitHub Comments

6reactions

mcguucommented, May 17, 2021

I do not think so. If there is a Content I do not want to use it .

just keep it simple.

you can write layouts to it.

3reactions

ronnygunawancommented, Sep 24, 2021

I do not think so. If there is a Content I do not want to use it .

just keep it simple.

you can write layouts to it.

The purpose of having Content is to expand the clickable area to text next to the checkbox. It’s really inconvenient having to click on the small box and not being able to click on the text to check the checkbox.