github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-03-09 07:13:35 -05:00
Code Issues 219 Packages Projects Releases 2 Wiki Activity

Create a new service that tracks every user mutation #449

New Issue
Open
opened 2025-11-01 20:56:21 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-01 20:56:21 -05:00
Owner
Copy Link

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.
GiteaMirror added the area/internal-code label 2025-11-01 20:56:21 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/caldav
area/filters
area/frontend
area/gantt
area/internal-code
area/typesense
bug
changes requested
confirmed
dependencies
enhancement
good first issue
help wanted
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label area/internal-code
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#449
Delete Branch "%!s()"

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?