Redux-observable: Linked documentation in warning is not found

[dance2die]

EDIT BY @jayphelps: Google killed the link, but I believe it pointed to the original issue ticket here: https://github.com/redux-observable/redux-observable/issues/389

---

Description

The link, https://goo.gl/2GQ7Da in warning does not exist.
(_Error occurs even with all ad-blockers turned off_)

The warning below is found here - https://github.com/redux-observable/redux-observable/blob/16f083d405/src/createEpicMiddleware.ts#L49

warn(
  'this middleware is already associated with a store. createEpicMiddleware should be called for every store.\n\nLearn more: https://goo.gl/2GQ7Da'
);

Additional Context

These are not directly related but added for completeness.

• Redux-Observable version: v1.2.0
• Site framework: Next.js v9.1.4
• OS: Windows 10 build 1903.
• Browser: All browsers (Used Brave in the screenshot)

Searching for https://goo.gl/2GQ7Da in the issue shows Server Side Rendering Documentation (not a dupe), which I will be checking out for the warning.

[jayphelps]

Oh bummer. Google stopped supporting their old shortened links and it's now a Firebase thing. Thanks for the heads up! The next release will fix the warnings, though unfortunately it doesn't seem like I can retroactively fix the old ones. 😢

[dance2die]

You're welcome & thank you for looking into the matter~

[vvscode]

+1 for the issue - how about the fix? at least post the correct link here ))

[jayphelps]

I'm not sure what that link pointed to unfortunately since Google killed them. It might have pointed to the original issue ticket: https://github.com/redux-observable/redux-observable/issues/389

The solution depends on exactly what you're doing, but the most general description of the solution is that you (currently) cannot reuse an epic middleware with more than one store, you have to call createEpicMiddleware() and run the root epic each time you create a new store.

While testing epics using a mock redux store isn't _wrong_--feel free to continue to do so--you might consider testing epics using the RxJS TestScheduler with marble diagrams, instead.