Router Store: Update stateKey definition to take a string or selector

[brandonroberts]

Describe any alternatives/workarounds you're currently using

Other information:

If accepted, I would be willing to submit a PR for this feature

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

Follow-up to #1294. Allows more flexibility about where you want to place your router state in your state object. Leave a comment if you are willing to take on this PR.

[koumatsumoto]

@brandonroberts
you mean we change StoreRouterConfig interface as below?

before

export interface StoreRouterConfig {
  stateKey?: string;
  serializer?: new (...args: any[]) => RouterStateSerializer;
  navigationActionTiming?: NavigationActionTiming;
}

after

export interface StoreRouterConfig {
  stateKeyOrSelector: string | Selector;
  serializer?: new (...args: any[]) => RouterStateSerializer;
  navigationActionTiming?: NavigationActionTiming;
}

[brandonroberts]

Yes, and add a test also

[koumatsumoto]

Thank you!
I'd like to take this issue if I could.

[brandonroberts]

👍

[homj]

I think the SoreRouterConfig (and the Selector proposed here) should be generic to prevent type warnings when using custom serializers (see #1457)