strictStateImmutability + RouterState.Full incompatible with each other

[luchsamapparat]

Enabling strictStateImmutability together with RouterState.Full as router state serialization leads to errors that are very hard to track down (see angular/angular#31523, #1937), so the runtime check documentation should probably include a warning that those to configurations are not compatible with each other.

And for future (major) releases the Minimal router serialization should maybe be the default...?

I would be willing to submit a PR for the docs ❤️

[X] Yes (Assistance is provided if you need help submitting a pull request)
[ ] No

[timdeschryver]

This is not the first time I see this question, so I agree that it would good to add a warning here.

Do you want to pick this one up @luchsamapparat ?

[luchsamapparat]

I'll create a PR on Friday 👍

[wawyed]

Sorry to bring up an old post but I'm using the MinimalRouterStateSerializer but I'm still getting CannotFreeze error from strictStateImmutability. Is this a regression?

I'm on version 14

EDIT: Looks like that if you have a router resolve with a class with Observables you won't be able to use ngrx router store as it won't be able to serialise the routerAction.payload.routerState on the routerReducer function