Document that setting a previously undefined property does not trigger a re-render.

Hi

I just stumbled upon a small “nice-to-know”.

If using useGlobal() in a simple (functional/stateless) component, the global state settings your are accessing must be initalized prior to the call to useGlobal(). This might be obvious to some, but I was wondering why my component would not re-render itself when updating the global, but as soon as I made sure to initialize the global beforehand, it started working.

Apparently this is not mentioned in the documentation, but if it is, then my apologies.

[kaa4ever]

Thanks the explanation, that makes perfect sense and I agreed with your decision to not use proxies for now. I wouldn’t regard this as any issue or drawback for using ReactN, it’s only nice to know beforehand, then it’s quite easy to initialise the state 😃

As a side note I must compliment your work on ReactN - we are moving from React with Redux to React with hooks and ReactN and so far the feeling is much better and the code much less cluttered 😃

[chrise86]

Hm, there is no way <Badge /> is mounted before that call. I had to resort to using the withGlobal method.