Create a new service that tracks every user mutation #2045

Open
opened 2023-04-06 14:53:17 +00:00 by dpschen · 4 comments
Member

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
Owner

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.

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.
Author
Member

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.
Owner

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

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

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

For now I only thought of in-memory. It might help plugging in persistence later.
dpschen added the
kind/feature
area/internal-code
labels 2023-04-11 22:02:14 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/vikunja#2045
No description provided.