satanTime

ng-mocks uses many undocumented and monkey patched things. For a proper PR, you need to provide a proper test which demonstrates the issue and its fix. Here, I see that...

[v14.13.0](https://github.com/help-me-mom/ng-mocks/releases/tag/v14.13.0) has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.

[v14.13.1](https://github.com/help-me-mom/ng-mocks/releases/tag/v14.13.1) has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.

[v14.13.0](https://github.com/help-me-mom/ng-mocks/releases/tag/v14.13.0) has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.

[v14.13.0](https://github.com/help-me-mom/ng-mocks/releases/tag/v14.13.0) has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.

Hi all. Give me please time on the weekend. I'll check PRs and fix this.

Hi all, could you also post as many code examples as you have with the issue and use-cases? So it would be easier for me to cover all of them...

Hey. It's my nest issue to fix. But I struggle to dedicate enough time to that. I guess you noticed that renovate stopped working. Now that should be fixed first.

[v14.13.1](https://github.com/help-me-mom/ng-mocks/releases/tag/v14.13.1) has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.

Hi @PieterjanDeClippel, I can release the current state this weekend. However, it doesn't include support of all new cool stuff Angular has added. That I plan to implement during the...