You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I can see, API Platform sends updates on insert/update/delete (\ApiPlatform\Core\Bridge\Doctrine\EventListener\PublishMercureUpdatesListener::onFlush) automatically. This causes performance problems if many entities are updated/inserted/deleted at once. In my case, I'm not listening to inserts and deletions, so it doesn't make sense to send the updates in the first place.
It would be great if some kind of configuration would be possible.
The text was updated successfully, but these errors were encountered:
This is true only with mercure=true on an entity right? I'd say that you should definitely override our PublishMercureUpdatesListener to have all the control you need. I've done so on few projects already. I'm having a hard time seeing how we could "configure" these updates unless coding the listener.
As far as I can see, API Platform sends updates on insert/update/delete (
\ApiPlatform\Core\Bridge\Doctrine\EventListener\PublishMercureUpdatesListener::onFlush
) automatically. This causes performance problems if many entities are updated/inserted/deleted at once. In my case, I'm not listening to inserts and deletions, so it doesn't make sense to send the updates in the first place.It would be great if some kind of configuration would be possible.
The text was updated successfully, but these errors were encountered: