v1.10.0

Enhancements and Fixes

Lots of updates in this minor version bump!

• The logic for the value of <Control.text> components was improved (see 8579917 for the technical details) in order to quell some of the "component is switching from uncontrolled to controlled" errors.
  • If the value is undefined, an empty string is rendered instead.
  • Otherwise, the normal text value (string) of the modelValue is rendered, as usual.
  • For <Control> (default control), the value is not messed with. It is up to your custom component to do proper value checking.
  • Related to #714, #733, #739
• Small dependency updates (#738) and tsdef updates (#740)
• The getValue prop, once internal, is now exposed to <Control>. See the docs for more info.
• Because of this, Control.checkbox was refactored which solves #725. The isToggle prop is also exposed, which lets you indicate whether the control acts like a "toggle" (that is, its value remains the same but it affects the overall model value, like a checkbox or radio button).
• React 15.5 came out which deprecated the internal use of React.PropTypes, so that was taken care of.