- 🇩🇪Germany c-logemann Frankfurt/M, Germany
@eiriksm You are right, when checks only run if there are fields configured to extract links this code is not needed any more. So I close as outdated.
Currently the linkchecker operates on entity hooks for insert, update and delete. There is only switch of if if ($entity instanceof LinkCheckerLinkInterface) operates link extraction on all entities if ($entity instanceof FieldableEntityInterface). With a configuration option to include and/or exclude entity types and/or bundles we can extend configuration options in D9 as we have in D7. And we get a tool to avoid problems like
#3203329: Support entities with non-numeric IDs →
even if it's just only a workaround until it's fixed. To solve such problem via custom code or to get a possibility for an own logic there should be a hook as a minimum solution.
Use for example an entity type which is currently incompatible like entityqueue: #3203329: Support entities with non-numeric IDs →
Discuss, decide and introduce a configuration option and as minimum a hook to allow problem solving via custom code.
Diskussion.
If we decide to introduce a configuration we need a UI for this.
Maybe a new hook but no breaking change on existing API.
Additional configuration data if config solution is decided.
Closed: outdated
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
@eiriksm You are right, when checks only run if there are fields configured to extract links this code is not needed any more. So I close as outdated.