satanTime

Hi @twjacobsen, what you do is expected and is exactly how the `.replace` works. However, it turned out to be a bug in angular itself. I've submitted a bug here:...

Hey @twjacobsen, Thanks for the update. Stay in touch then!

Hi @dtomaszewski, it's still blocked on Angular's side: https://github.com/angular/angular/issues/48432

Hi @maxs-rose, I've tried to reproduce, but couldn't get the same behavior. What I've seen was - during the test with and without `ng-mocks` memory spikes, and after all tests...

Thank you for the example, now I can see the issue and was able to get detached elements. ```ts import { CurrencyPipe } from '@angular/common'; import { Component, Inject, Injectable,...

Hi @cford256, that's a good FR. I'll take a look how it's possible to detect signals to mock them. At this moment, I would recommend something like [default observables](https://ng-mocks.sudo.eu/extra/mock-observables#permanent-fix): ```...

Hi @alexciesielski, thank you for reporting the issue. It looks like an angular issue. I tested on `[email protected]` and `[email protected]` and it works correctly. Could you confirm it still fails...

Hi @LPCmedia, could you create a min example with the failure? I cannot reproduce on my side: ```ts import { TestBed } from '@angular/core/testing'; import { MockBuilder } from 'ng-mocks';...

Also, could you check if this change solves the issue? [ng-mocks.zip](https://github.com/help-me-mom/ng-mocks/files/13403778/ng-mocks.zip)

And this should help to understand which module is causing the issue: [ng-mocks.zip](https://github.com/help-me-mom/ng-mocks/files/13403797/ng-mocks.zip)