null props considered differently in getDefaultProps vs. isRequired

[aweary]

Moving from the React repo, original issue: facebook/react#2166

[jharris4]

Thanks for linking this issue! Interesting that 39 people reacted with a thumbs up to +1 for isDefined / isRequired

There's a lengthy discussion about the topic of null props going on in the PR: #90

[martpie]

For those interested in a workaround, you can always define your own propTypes:

// Number or null
foo: function(props, propName, componentName) {
  if (props[propName] !== null || typeof props[propName] !== 'number')
    return new Error(
      'Invalid prop `' + propName + '` supplied to' +
      ' `' + componentName + '`. Validation failed.'
    );
}

And it is perfectly possible to make it re-usable as it is a function.

[virgofx]

@KeitIG I think the issue is that people prefer an out of box solution to handle such a common use-case.

[martpie]

I totally agree, I am just leaving this solution in case of someone not knowing how to tackle this in the meantime. (like me, this morning).

The check should be

foo: function(props, propName, componentName) {
        if (props[propName] !== null && typeof props[propName] !== 'number')
            return new Error(
                'Invalid prop `' +
                    propName +
                    '` supplied to' +
                    ' `' +
                    componentName +
                    '`. Validation failed.'
            );
    },