- Issue created by @jhedstrom
- 🇺🇸United States jhedstrom Portland, OR
I added some proof-of-concept code that works. Some refinement would be needed to get this fully working across all entity types, etc.
- First commit to issue fork.
- 🇧🇬Bulgaria valthebald Sofia
I see some common approach with how AI translate module extracts textual data from (sometimes nested) entity fields - there is FieldTextExtractorInterface introduced in https://www.drupal.org/node/3464024 → and TextExtractor service that has extractTextMetadata/insertTextMetadata methods.
Can this be reused in content suggestions?
That would require some (minor) changes like moving the service and field plugins from ai_translate to ai module itself, but benefit IMO is bigger
- First commit to issue fork.
- 🇩🇪Germany marcus_johansson
I set this to Needs work because of breaking changes.
@valthebald - moving such a service to the core might make sense, Automators might need it as well. We should check and possibly plan for it, when you have time.
- 🇧🇬Bulgaria valthebald Sofia
@marcus created 📌 Move TextExtractor service to AI core Active and assigned to myself. Will try to submit a proposal by Monday EOD