Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a plugin to replace the Stash-Split-Duplicate-Merged-Files. Which if this pr is merged the Split Duplicate files plugin reference will also need deleted from https://docs.stashapp.cc
Rather than splitting anymore. One reason if that the old plugin could not work on images as you can't take an image file id and create a new image with it in Graphql. And since most image/scene objects that contain multiple files - these files in the case of scenes have identical Phashes, so are safe to just delete (With exception to manually merged scenes.). In the case of images the multiple files are identical checksums, so are relatively safe to delete and manual merging of image objects is not possible.
The plugin offers the generation of an ignore tag, to bypass objects with multiple files you don't want deleted.
Apart from the Create Tag task. It offers 4 other tasks. 2 each for scenes and images.
The first kind is just to scan for objects with additional files and delete them
The second kind is to take the paths of the files to be deleted from an object and prefix them with "File: " (For easier searching later) and append them to any current urls if any and update the object.
These tasks are in the case if a user finds that extra files of an object that their paths may contain useful unretrievable metadata if just deleted apart from the primary file. So just to record these in the urls field, since there is no other field adequate for such a thing.
I know that's not what the urls field is designed for, but is useful in this case.
Thanks