docs: ui.radio_group

[AkshatJawne]

Closes #756

[AkshatJawne]

Failures here are unlike other PRs, still investigating docstring to determine how to fix failure.

[AkshatJawne]

Should be good now to review

[dsmmcken]

I see you added value everywhere. Is value always required? I thought it was optional and used the label? If so, I would show some options like that.

[AkshatJawne]

@dsmmcken This is interesting, just tried some examples, and it appears that if we do not currently set the value to be the label, if the value is not provided.

The value by default is set to None, so I guess there are two options:

a. Create a ticket to make it so that it sets the value to the label by default, and then include the fact that the value is an optional prop.
b. Do not make any changes to the current logic, and enforce that users have to set value

I am more in favor of A, but open to either

[dsmmcken]

I think it should work automatticaly as you describe with option A. I mean that's what you had initially actually tried, so it seems like thats how one would expect it to work. This of course only applies if contents of the label are a string, and not anything more complex (not sure if it accepts icons + text for example, in which case a value would be required.

@mofojed thoughts?

[AkshatJawne]

It appears that it accepts icons + text, so in cases like this, we would have to have a value set.

So, I think we should create a ticket where we make the value default to the label, if the label is text. Otherwise, if the label is an icon + text for example, we make it so that value has to be passed in.

@dsmmcken @mofojed

[dsmmcken]

@AkshatJawne Please ticket this, and also we should make sure checkbox/checbox_group also behaves the same way, as looking at checkbox docs I don't see it talking about the value prop at all.

[AkshatJawne]

Created ticket: #765