Create a new service that tracks every user mutation #448

New issue

Open

opened 2026-02-27 15:03:47 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-27 15:03:47 -05:00

Owner

Originally created by @vikunja-bot on GitHub (Apr 1, 2025).

Original issue by dpschen on 2023-04-06T14:53:17.000Z

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

Original issue on Gitea

@kolaente commented on 2023-04-06T16:05:37.000Z:

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 on 2023-04-11T12:04:10.000Z:

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.

@kolaente commented on 2023-04-11T16:20:56.000Z:

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

dpschen commented on 2023-04-11T22:01:34.000Z:

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

Originally created by @vikunja-bot on GitHub (Apr 1, 2025). _Original issue by dpschen on 2023-04-06T14:53:17.000Z_ 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 [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/2045) --- _**@kolaente** commented on 2023-04-06T16:05:37.000Z_: 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 on 2023-04-11T12:04:10.000Z_: > 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. --- _**@kolaente** commented on 2023-04-11T16:20:56.000Z_: That makes more sense, thanks for the explanation. Would this only be in-memory? Or persisted somewhere? (localstorage or api) --- _**dpschen** commented on 2023-04-11T22:01:34.000Z_: For now I only thought of in-memory. It might help plugging in persistence later.

deekerman added the

area/internal-code

label

2026-02-27 15:03:47 -05:00

No milestone

No project

No assignees

1 participant

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

starred/vikunja-go-vikunja#448

No description provided.

Rows
Columns