Closed (fixed)
Project:
Crop API
Version:
8.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
30 May 2019 at 15:07 UTC
Updated:
26 Nov 2025 at 02:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
amateescu commentedThis should do it.
Comment #3
berdirHm, not sure about this.
Yes, this is doesn't provide a UI, that happens through modules like focal point or image_widget_crop.
But.. that doesn't make it internal? If you'd reimplement e.g. focal point in a decoupled site, then you need to be able to write/update crops through an API?
Comment #4
amateescu commentedI agree with #3, marking it as internal was just a workaround because we lacked proper support for "ignoring" processing some entity types in a workspace. That will no longer be the case after #3101671-13: Add mechanism to have workspaces skip processing entity types, so I'm closing this issue.
Comment #5
amateescu commented#3101671: Add mechanism to have workspaces skip processing entity types was recently committed to Drupal core, and it provides a way for entity types to be "ignored" by workspaces, by using the
Drupal\workspaces\Entity\Handler\IgnoredWorkspaceHandlerentity handler.That handler is only instantiated by the Workspaces module, so it's safe to add it in the entity type annotation even though the Drupal core release which includes it (10.3) is not released yet.
Comment #6
amateescu commentedComment #8
phenaproximaThis makes sense to me, and seems safe since as @amateescu points out, the handler is only ever instantiated by Workspaces. Committed and pushed to 8.x-2.x. Thanks!