[GH-ISSUE #267] Bug - Empty Snippet being saved #150

New issue

Open

opened 2026-03-03 01:10:26 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 01:10:26 +03:00

Owner

Originally created by @vedantpuri on GitHub (Apr 9, 2018).
Original GitHub issue: https://github.com/Clipy/Clipy/issues/267

If one tries to create a snippet inside a folder by clicking on add snippet on a certain folder in Clipy, an untitled snippet is created. However if I decide midway to abandon creating that snippet, it still creates an 'untitled snippet' with blank text stored in it.

Fix Suggestion:

Check if snippet title has changed before saving
Check if snippet actually contains something and isn't blank

The need for this is for shear usability purposes as it becomes tedious for the user to go and delete a snippet that he never intended to make in the first place.

Also after trying this out, I noticed that Clipy allows for duplicate snippet names in the same folder which might cause an issue (confusion for the user)

Experienced on macOS High Sierra 10.13.4

Originally created by @vedantpuri on GitHub (Apr 9, 2018). Original GitHub issue: https://github.com/Clipy/Clipy/issues/267 If one tries to create a snippet inside a folder by clicking on add snippet on a certain folder in Clipy, an untitled snippet is created. However if I decide midway to abandon creating that snippet, it still creates an 'untitled snippet' with blank text stored in it. Fix Suggestion: - Check if snippet title has changed before saving - Check if snippet actually contains something and isn't blank The need for this is for shear usability purposes as it becomes tedious for the user to go and delete a snippet that he never intended to make in the first place. Also after trying this out, I noticed that Clipy allows for duplicate snippet names in the same folder which might cause an issue (confusion for the user) Experienced on macOS High Sierra 10.13.4