react-cosmos: Using `set` to set reduxState in test context doesn't update the actual st.

What’s up?

Setting reduxState in test context doesn’t update the actual state.

Mkay, tell me more…

Turns out this test from the docs doesn’t actually work…

test('responds to new state', () => {
  const newState = { showWarning: true };
  set('reduxState', newState);
  expect(getWrapper('.btn').hasClass('warning')).toBeTruthy();
});

This is my bad for not testing it in my other PR the other day. Once the store has been created in the redux-proxy, it takes over management of the store state (as it should) and doesn’t do anything with an updated fixture props. I tried setting the ‘alwaysCreateStore’ option on the proxy but that doesn’t work (it only does it on the constructor, not componendDidUpdate.

Now I’m also not sure that the other proxies also respond to the fixture being updated as a lifecycle change and respond accordingly.

I’m wondering what the best way to go about doing this would be? Happy to help (since I created a buggy ‘feature’).