Update radio.html

[kamilkisiela]

@bbeyssac Currently templateOptions.className is pointing to element with ngModel directive so in that case it is mdRadioGroup.

It would be nice if each mdRadioButton had classNameProp or something similar to valueProp and labelProp convention. So user would be able to add different classes for different options.

{
  type: 'radio',
  key: 'name',
  templateOptions: {
    label: 'Name',
    className: 'custom-options',
    labelProp: 'firstName',
    valueProp: 'id',
    classNameProp: 'className',
    options: [
        { firstName: 'Sarah', id: 1, className: 'bold'},
        { firstName: 'Jessica', id: 2, className: ['bold', 'italic'] },
        { firstName: 'Parker', id: 3 }
    ]
  }
}

Do you want to try? :) I can help you

[bbeyssac]

This code don't works if ng-class="to.className" is not defined in the "radio.html" template.

formlyConfigProvider.setType({
    name : 'boolean',
    extends : 'checkbox',
    defaultOptions : {
        templateOptions : {
            className : 'md-primary'
        }
    }
});

This case works, if i force class name in the fields form : { "key" : "confidential", "type : "boolean", "templateOptions" : { "className" : 'md-primary' } }

I don't undersand why.

[kamilkisiela]

@bbeyssac I don't know exactly what you want to achieve and what's the problem. Could you explain it to me a little bit?