ActivityWatch / ActivityWatch/aw-webui
Tagging Feature
- Langage dominant
- TypeScript
- Étoiles
- 151
- Forks
- 179
- Merge moyen
- 1 j 20 h
- PR mergées (30 j)
- 28
Description
I've created a Proof of Concept (POC) for tagging, which has proven to be very helpful for my use cases. I would like to contribute this feature by submitting a pull request (PR), but I have several questions:
[POC.webm](https://github.com/ActivityWatch/aw-webui/assets/70476337/fc68927b-6a92-4496-8bce-7eb8a1e2dd0e)
- Should offline tagging be implemented for the stopwatch watcher or another custom watcher?
- Should it be integrated into the timeline view, or should there be a separate view specifically for offline tagging?
- Regarding the [refetching of events in the eventEditor component](https://github.com/ActivityWatch/aw-webui/commit/c0970023f931c406db70f2cecab4e51d1b8bdb0a#diff-c27f7283974edb48777c644fc2f13d8a88621f2dd3b47b39ff0e1a4e432bdb2a), I am currently passing an edited event to the eventEditor. Is there a case that I am not aware of that necessitates refetching events?
- How should I implement this feature to ensure it is included in the next stable release?
Note: Currently, I am triggering a re-render to update the graph, which is causing a delay. I understand that this should be optimized, and I am open to suggestions for improvement.
Additionally, I'd like to mention that this would be my first real contribution to the project. I appreciate any guidance and support from the community.
Related: https://github.com/ActivityWatch/activitywatch/issues/95
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Évaluation
Cette issue n'a pas encore été évaluée.