[RadioButton] Bug custom wrapper in RadioButtonGroup

[peterbartos]

Cannot use a customized-wrapper-RadioButton inside RadioButtonGroup, because it gets replaced with standard RadioButton component during render.

RadioButtonGroup render should reuse the same RadioButton component instead.

[egonvb]

I ran into the same problem, I've created a RadioButton which is wrapped in a Paper component. However due to the rendering method used in the RadioButtonGroup, the component got replaced. I replaced the rendering method with the following, this way the wrapping still works.

`render() {

const {prepareStyles} = this.context.muiTheme;
const options = React.Children.map(this.props.children, (option) => {

  const {
    name, // eslint-disable-line no-unused-vars
    value, // eslint-disable-line no-unused-vars
    label, // eslint-disable-line no-unused-vars
    onCheck, // eslint-disable-line no-unused-vars
    ...other
  } = option.props;

  return React.cloneElement( option,{
      ...other,
      ref           : option.props.value,
      name          : this.props.name,
      key           : option.props.value,
      value         : option.props.value,
      label         : option.props.label,
      labelPosition : this.props.labelPosition,
      onCheck       : this.handleChange,
      checked       : option.props.value === this.state.selected
  });
}, this);`

the wrapped component looked like this

class Answer extends Component{ render(){ return <Paper> <RadioButton {...this.props} </Paper> } }

Note: wrapper has to be a class, a stateless function cannot be used because ref is used by the radiobuttongroup.

[oliviertassinari]

We have been porting the component on the v1-beta branch. We reimplemented it from the ground-up. While we haven't tested it, I think that the issue is most likely fixed on that branch. Hence, I'm closing it.
Still, we will accept PR fixes until v1-beta takes over the master branch.