Cache break of MockComponent

[satanTime]

Unfortunately, there's an issue with cached component because cache doesn't respect 2nd argument of MockComponent and we have the same problem as MockPipe has when we pass there different transformers.

df56334

A possible solution is to redo this feature in a proper way.

• It can be redone with the MockBuilder as configuration parameters for the .mock method Allow mocking an internal vs external module #44.
• maybe a call of TestBed.overrideComponent on the cached mock can help there.

@askarby, could you provide a test sample how you use it in your project?

[satanTime]

Hi @ike18t,

I hope you are fine.

I was thinking about df56334 and, being honest, can't find a way how to reimplement it with the correct cache support.

Because

MockComponent(MyComponent, {template: 'a'});

and

MockComponent(MyComponent, {template: 'b'});

and

MockComponent(MyComponent);

simply don't work all together.

We can implement createMockComponent(), createMockDirective() etc. as a replacement of the requested functionality, but still I don't understand the goal of providing totally different config for an existing component. If we want to replace the original component with something totally custom - now it can be achieved with MockBuilder.replace.

Please let me know your decision and I'll prepare either pure revert or revert + createMock... functions.

[satanTime]

Hi @askarby,

might you provide an example how you use it? Unfortunately, otherwise I need to deprecate it and remove in v11.