Greg Kopp

Can't you use the **@select$** decorator to do this?

Abstract your redux code to a separate state service and then use the MockNgRedux module. Here is an example. I've stripped out some business logic and dumbed this down a...

I will add that this pattern keeps all of your redux in one place and only requires one place to mock the redux. By injecting the state service into your...

Whatever is acting on your action (in an Epic, I would assume) should dispatch another action indicating such. ie.: Dispatch: DATA_REQUESTED Epic: Calls API and gets data Dispatch: DATA_RECEIVED Your...

Have you tried using fakeasync and tick?

Your test here might be going a bit too far. And you shouldn't need to use the TestBed for this. If all you want to do is unit test your...

Even if you are injected http, you can still mock that class in your epic (although I am not a fan of that approach). I think these articles are very...

Is there any movement on this? Part of a CI/CD pipeline will break a build if the word "error" appears in a particular log. Since this references this URL: https://angular.io/errors/NG0912...

But that's just a hack, it's not a solution. I should not have to add anything to a non-routable component to make it work.

We were informed that this was an erroneous classification and that lodash does NOT contain the vulnerability. The issue can be closed.