feat: Add events for row added and row updated

[come-nc]

No description provided.

[enjeck]

@come-nc Why do we need these events for?

[enjeck]

Ah, I guess related to Workflows?

[come-nc]

Ah, I guess related to Workflows?

Yes!

[juliushaertl]

@blizzz What's your thought on just returning the entity directly here?

I'm unsure if we shall expose the internal row entity through events, rather expose specific getters or use a serializable event as #1103 mentioned

[juliushaertl]

@come-nc To evaluate what we want to pass along in the event, could you share more insights on the use case you're covering with your workflow task?

[come-nc]

@come-nc To evaluate what we want to pass along in the event, could you share more insights on the use case you're covering with your workflow task?

Usecases are multiple:

• Have a workflow react to data inserted in a table (for instance a user is created in another application when a line is added to a table).
• Have a workflow react to a modification of a row (typically a boolean column is checked to approve a vacation request or something, triggers a chain of events).

I feel like putting the whole row content information in the event is too much because it may be a lot of data, while putting only the id allows to fetch the data from the API if needed. Not entirely sure. Maybe content but capped at a given maximum length would make sense?

The event will need to be serialized by implementing upcomming OCP\EventDispatcher\IWebhookCompatibleEvent interface.