Closed CalebMorris closed 9 years ago
The current (0.1.0) behavior of MomentPropTypes.momentString.isRequired is defaulting to the optional behavior and isn't throwing a warning as I would expect. I'm not sure why this is occurring, but will investigate.
0.1.0
MomentPropTypes.momentString.isRequired
ref #4
The current (
0.1.0) behavior ofMomentPropTypes.momentString.isRequiredis defaulting to the optional behavior and isn't throwing a warning as I would expect. I'm not sure why this is occurring, but will investigate.ref #4