Determine type of file action
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- operating-systems
Research direction
The issue names no files or tests, so start by reading the watcher package API and its filesystem-event handling. Trace how file changes are currently reported, then determine how created, changed, deleted, and renamed events could be distinguished; done means callers can select different actions for those event types.
Written by the indexing model from the issue text.
Description
Thanks for this great package! I have previously used powershell (FileSystemWatcher), however this package works much easier. The powershell solution I used before did however have the option to perform different actions based on the type of change. For instance a different function can be called in case a file is changed, created, deleted or renamed.
I was wondering if something similar could be achieved with this package as well? I can find out what happened manually, based on the name of the file. But would be nice if there is a more elegant solution.
- Dominant language
- C++
- Stars
- 38
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from r-lib/watcher
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·