- Issue created by @wouters_f
- 🇧🇪Belgium wouters_f Leuven
in this sample you see that you dont have to wrry about api calls or api keys.
The ai module arranges that for you, it just provides you withAI's you can use.
It would be great if your module uses this system too. - 🇫🇮Finland jhuhta
The suggestion sounds very reasonable. By the time of writing this module, the need was to make it as simple as possible and match the requirements from the client. Writing the LLM client appeared to be so simple that adding a dependency to the AI module ecosystem felt a bit overkill, but I'm ready to reconsider that. A working MR would make the change easier. An upgrade path would also help.
But now this current implementation provides also a possibility to include service provider specific processing, which I'm not sure would be possible.
- Merge request !9Issue #3460682 by jhuhta: Make the module part of Drupal AI ecosystem → (Closed) created by jhuhta
- 🇫🇮Finland jhuhta
Crediting @wouters_f for the idea and support to make this happen.
It also required writing a new operation type for the AI module → and a provider module for DeepL → .
Fixed in 2.0.x branch.
Automatically closed - issue fixed for 2 weeks with no activity.