Can you add tests? 🙏🏻

@PineappleIOnic @TorstenDittmann could you explain what is the core issue? is the API lifecycle cut mid request? why can't we rely on the original trigger. Adding and managing each event per request is not the best design choice if we have other options.

@PineappleIOnic @TorstenDittmann could you explain what is the core issue? is the API lifecycle cut mid request? why can't we rely on the original trigger. Adding and managing each event per request is not the best design choice if we have other options.

First of, we can't rely on the original trigger since the events have different payloads. Also triggering resets the Event class, which would require more work as well.

Since we have 2 different payloads, we have to find another way than just relying on the response payload.

That's why I suggested doing this for now and have a discussion around a possible implementation.

@TorstenDittmann we do have an option to overwrite the default event data without completely replicating the functionality like implemented here:

@TorstenDittmann we do have an option to overwrite the default event data without completely replicating the functionality like implemented here:

appwrite/app/controllers/shared/api.php

Lines 190 to 192 in a585a90

	if(empty($events->getParam('eventData'))) {
	$events->setParam('eventData', $response->getPayload());
	}

- why isn't the original event being triggered?

That was my first suggestion. Then we would still had to clone it, since the event object is reset after the trigger.

Any progress on that? 👀

PR is heavily outdated, creating a new one using the new event system...