Create a new service that tracks every user mutation #3359

New Issue

dpschen · 2023-04-06T14:53:17Z

dpschen commented

2023-04-06 14:53:17 +00:00

useful for logging, activity history, undo, crdt, quick-actions (centralized methods for everything), etc

We can roll this out step by step. In the begining only one store

useful for logging, activity history, undo, crdt, quick-actions (centralized methods for everything), etc We can roll this out step by step. In the begining only one store

konrad commented

2023-04-06 16:05:37 +00:00

Why would be the purpose of this? If we want to have an activity lot (like an audit log) that should be done in the api.

dpschen commented

2023-04-11 12:04:10 +00:00

Poster

Why would be the purpose of this? If we want to have an activity lot (like an audit log) that should be done in the api.

I meant logging in the frontend. Having one central place for this makes stuff liek user history much easier.

I could have created an issue saysing stuff like:

Enable undo history everywhere
prepare crdt integration
create central service that centralised methods for quick actions

All of theses tasks might still make sense isolated in the future. But then they could build upon this service and will be easier to build.

> Why would be the purpose of this? If we want to have an activity lot (like an audit log) that should be done in the api. I meant logging in the frontend. Having one central place for this makes stuff liek user history much easier. I could have created an issue saysing stuff like: - Enable undo history everywhere - prepare crdt integration - create central service that centralised methods for quick actions All of theses tasks might still make sense isolated in the future. But then they could build upon this service and will be easier to build.

konrad commented

2023-04-11 16:20:56 +00:00

That makes more sense, thanks for the explanation. Would this only be in-memory? Or persisted somewhere? (localstorage or api)

👍 1

dpschen commented

2023-04-11 22:01:34 +00:00

Poster

For now I only thought of in-memory. It might help plugging in persistence later.

👍 1

dpschen added the

kind/feature

area/internal-code