-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Adjust image editing naming schema #22580
Copy link
Copy link
Closed as not planned
Labels
REST API InteractionRelated to REST APIRelated to REST API[Block] ImageAffects the Image BlockAffects the Image Block[Feature] MediaAnything that impacts the experience of managing mediaAnything that impacts the experience of managing media[Type] DiscussionFor issues that are high-level and not yet ready to implement.For issues that are high-level and not yet ready to implement.[Type] EnhancementA suggestion for improvement.A suggestion for improvement.
Metadata
Metadata
Assignees
Labels
REST API InteractionRelated to REST APIRelated to REST API[Block] ImageAffects the Image BlockAffects the Image Block[Feature] MediaAnything that impacts the experience of managing mediaAnything that impacts the experience of managing media[Type] DiscussionFor issues that are high-level and not yet ready to implement.For issues that are high-level and not yet ready to implement.[Type] EnhancementA suggestion for improvement.A suggestion for improvement.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Follow-up from #21024 (comment)
If we had a reference to the original, unedited, image stored and we did the batched edits from #22579, we could better calculate a name for images. The order of operations is still important, so rotate-90-scale-300x255 is different from scale-300x225-rotate-90.
I like that the current implementation includes the unique edits that were made to the image so an edit doesn't have to be made if there's already a matching filename. It also has the benefit of making it easy, when browsing your media, to know which edits have been made if you had a couple different crops and were comparing between the two. A more reliable way to test for sameness could be to store an checksum of the image and compare against that instead.