[InteractsWithLiveComponents][Mocking]

[GrinWay]

Is there any way to mock a dependency container when form is submitted

I was not able to get mocked http_client when form was submitted

Maybe it's because Live Component actually makes another request to render the component...

Well... Question is: Is it possible to get mocked services where twig component renders (save method for instance, for saving entities when form submitted)

Because when I try to mock it I get a real http_client
I mean: MY TEST USES MOCKED VERSION OF http_client
but when form is submitted during the same test: I GET A REAL htt_client ON FORM SUBMITTION CODE SIDE

[Kocal]

Hi, just to be sure, you want to mock services used by your components, like your database, or to mock the HttpClient used by createLiveComponent()?

[GrinWay]

All I want is to get mocked services (http_client) on the twig live component side:

1. I'm inside the test
2. Tests have mocked dependencies
3. I create live tiwg component with createLiveComponent
4. Send the form
   (5) And exactly here when form is submitted (save method for instance) I want to have the same not rebooted container

So is it possible?

Because in my Live Twig Component when the save method executes an http_client request and I constanly get a real http_client result (actually it's a telegram message) but it would be better during that tets I actully wouldn't get a real message to my test telegram bot

[GrinWay]

Actually you understood me correctly

I'm looking for a way to get an origin service container for both:

1. actual tests
2. and live components' code they use

[GrinWay]

Well, after a long research I still didn't get mocked container for a Twig Live Component code

Problem: Live Component uses not a test container but a real (I guess a new created symfony container)

What a pity

Even when I use Panther E2E tests, make a request to the page with live components and interact with live form I still deal with a rebooted container and all of http client requests make a REAL request

It seems to me that I had to mark this issue with a bug badge