ImageOptim / ImageOptim/ImageOptim

Atomic file updates?

Open
#284 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
10k
Forks
478
PR merge metrics
No merged PRs in 30d

Description

I have ImageOptim configured as a folder action on several folders, including my Dropbox screenshots folder. That means that every time I upload an image I get an error from Dropbox asking whether I want to delete the file from every device because ImageOptim renames the file to a temporary filename until it's done working. This even broke some sharing URLs if they were created in the interval while ImageOptim was working

It would be nice if it either worked entirely with temporary files (i.e. in $TMPDIR) or left the original file alone until it was finished so there was never the case where a filename cycles in and out of existence over a minute or so.

Contributor guide

No contributing guide indexed for this repository

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

The issue names no files or tests; start by locating the folder-action file handling and reviewing how temporary filenames are currently used. Done means processing no longer makes the original filename disappear or change during optimization, while preserving the requested optimization behavior.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.