Ok I think I like this, having it warn always in this case even though it is legal. Because it will prompt the developer to explicitly specify the key as null or undefined if it is a legal path. But, I think this fix highlights that #38 (default value at subtree) is important, because it would provide a mechanical way to specify that this key is legally null, but also not have to specify all keys of the object up front at initialization, but rather in the component that needs it, much like getInitialState lets us specify default values in the component that needs them.
Ok I think I like this, having it warn always in this case even though it is legal. Because it will prompt the developer to explicitly specify the key as null or undefined if it is a legal path. But, I think this fix highlights that #38 (default value at subtree) is important, because it would provide a mechanical way to specify that this key is legally null, but also not have to specify all keys of the object up front at initialization, but rather in the component that needs it, much like getInitialState lets us specify default values in the component that needs them.