Cannot mock child component's DI services about ng-mocks HOT 4 CLOSED

The main question I have is why would you want to? It seems like this request stems from a deeper issue of the parent component having too much context on what is going on under the hood of the child component.

For something like a provider where it is a singleton, it would make more sense to DI it into the parent and use the provider that way which would cut out the middle-man of the child component.

from ng-mocks.

In our case Child is a Grid and Parent is a View. Service inside Child is not a Singleton, it's a instance-related and provided with bunch of other services via providers for Child component declaration.
EG we have DaatsourceService and displaying somewhere in Parent number of loaded rows.

from ng-mocks.

Gotcha.

MockedComponents are intended to be shallow and only consist of inputs and outputs. When I've encountered similar issues to this in the past where I need the mocked component to have additional implementation detail I typically query for the component and extend it (via a mocking lib or just assignment) prior to the behavior that has the expectation of the additional implementation existing.

from ng-mocks.

Hi everybody, possible fix #88
@Lonli-Lokli, could you check whether it solves your issue?
There's no spy on it, but at least it shouldn't fail.

from ng-mocks.