teamtype / teamtype/teamtype

Detect changes by external tools while files are opened in editors

Open
#312 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Rust
Stars
1.9k
Forks
54
Avg merge
2d 20h
Merged PRs (30d)
3

Description

Issue

In #303, we enabled this. In #310, we removed it again, because of an issue with VS Code.

Our suspicion: Our watcher picks up write events done by the daemon itself, which causes a full delete of the content, and then a restore.

To reproduce

  1. Be on a daemon version without ownership concept.
  2. Have a peer type into a file while you move your mouse out of VS Code.
  3. The watcher will pick up a full deletion + restore.

Possible solutions

Options:

  1. Have the watcher ignore file operations done by the daemon.
  2. Debounce the watcher.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing issues #303 and #310, then reproduce the delete-and-restore behavior with VS Code while a peer edits a file. Done means external edits are detected without daemon writes triggering a full deletion and restore; the issue leaves the choice between ignoring daemon operations and debouncing unresolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.