Preventing modifications of the existing state

[slawojstanislawski]

Many people use ngrx-store-freeze, which deep-freezes the state so that one didn't modify an existing state during development. If that's used, applying changes to the state object passed to the @Action-decorated function (e.g. state.loading = true) will result in TypeError: Cannot assign to read only property 'loading' of object '[object Object]'. I tested that with these changes the error doesn't occur, as the modification would then be applied to the new state instance.

[lanovoy]

Why state was renamed to store?

[slawojstanislawski]

After building and testing, during PR preparation I made some changes and introduced wrong variable name by mistake. I corrected the variable name.

[amcdnl]

I wanted it to do this so you don't have to spread every single time when you make a small modification.

[slawojstanislawski]

Alright, but when I tried it with ngrx-store-freeze, which I'm using to ensure the state remains immutable, an error was thrown, and the state modification was small, I toggled a boolean. I like having store freezing as this 'safety net' but I also wanted to refactor my app to use ngrx-actions, and with the current implementation it's one or the other.

[keitoaino]

Any progress on this PR? :)

[slawojstanislawski]

I would prefer to use the original version instead of publishing a forked repo to npm. If there's no intention for merging it, could you please close the issue, as I'm a bit stuck in indecision as how to proceed :)