Create a new service that tracks every user mutation #2045
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#2045
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
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:
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.
That makes more sense, thanks for the explanation. Would this only be in-memory? Or persisted somewhere? (localstorage or api)
For now I only thought of in-memory. It might help plugging in persistence later.