Feature request: have Context.Provider throw error if missing `value` prop

Just about every time I set up a new Context.Provider, I end up accidentally specifying a values prop rather than value. While it’s a minor error, generally I build the container in which the provider resides and commit it to the code base before I ever use it. It’s only later when I go to use it that I realize I did it again. Since the Context.Provider seems pretty much useless without a value prop specified, I’d love it if there was a prop error if it is missing… especially if another prop is defined on the Context.Provider instead.

[gaearon]

I think it does make sense to warn if !('value' in props). Want to send a PR?

[brunogonzales]

@charlie1404 you can totally take this off my hands, I haven’t started working on it yet. Please tag me on your PR as I would like to know the solution too.