Actions without types throw an error rather than return the default state

In my test setup code I have this line:

test.beforeEach(t => {
  const initialState = reducer();
});

where

const reducer = handleActions({ ... }, { /*initial state*/});

However, the first method throws an error because:

and in the transpiled source it looks like action.type.toString() is called unguardedly. Now, maybe I’m misunderstanding how FSAs work, but I think it makes sense for a reducer test to be able to check that the initial state is returned when the action type is missing. I can try to make a PR for this as well, if you think I’m correct about the expected behaviour.

If not, could you please fill me in on what I’m missing? Thanks!

[JaKXz]

Sorry for the duplication/noise, and 🙏 for a great project! I thought I’d searched the issues properly but I guess not.

[JaKXz]

Yeah at this point it’s just 🚴🏚-ing about test setup code, I can’t imagine a real example of having an undefined action or action type being dispatched. And I think I understand the argument that having the “robustness” to handle that is more bad than good.