>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3454976. --> Reported by: [marcus_johansson](https://www.drupal.org/user/385947) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Currently the bundles are Enums that might be problematic because they are not extedable and can't really have any functions attached to it. Also bundles is a very generic name, operation type, which becomes provider operation type is easy to understand what the purpose is.</p> <p>We should move this to a interface system with a base operation type, that defines a base normalized input provider interface and base output provider interface with a required normalize function in it, that each of the operations must integrate.</p> <p>The inputter will however take both any normalized interface that the operator creates or any mixed input for ease of use.</p> <p>The invokeResponse will then be in charge of normalizing the input and the output, so that you can have metadata attached to the output. This will make sure that both the case of having any type of operation being agnostic is possible, but for people that just want the quick fix to use the array in and array out method from OpenAI, this is also possible.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <ul> <li>Rename it to Operation Type instead of Bundle.</li> <li>Do not use a Plugin system for it, it does not need to be that flexible. An interface is enough.</li> <li>The interface constructor defines how to to create it and how a DTO would look like.</li> <li>The DTO would have both the normalized response and the raw response as well as any metadata that wants to be given, since its a DTO certain type of usual metadata can be defined.</li> <li>The providers then just implements the interfaces that they support.</li> <li>The input and output can still take mixed for developers that don't care about reusability, for developers that care about reusability they can use the interface.</li> <li>If a wrapper function is needed in the ProviderClientBase then we can take the interface as an initial parameter, similar to how the bundle enums works now.</li> </ul> <ul> <li><del>Create a OperationsTypeInterface that is what is today the enum bundle that is a Plugin system. This will have two methods (at least for now), that is inputInterface and outputInterface, that set the interface for that specific bundle (see below).</del></li> <li><del>Switch so that the LlmProviderInterfaces sets which operators it can take.</del></li> <li><del>Create a NormalizedInputInterface that has no methods at all.</del></li> <li><del>On the $input require mixed or a Interface that implements the NormalizedInputInterface.</del></li> <li><del>Add a method to the LlmProviderInterfaces that is called normalizeInput that takes an NormalizedInputInterface and normalizes this into the format that specific provider requires.</del></li> <li><del>Create a NormalizedOutputInterface that has the method validateNormalizedOutput that validates the normalized output for the operation, metadata that stores an array of any metadata the API might create.</del></li> <li><del>Add a method to the LlmProviderInterface that is called normalizeOutput that takes an answer and normalizes it according to the documented normalization in the NormalizedOutputInterface and then validates it and also takes metadata that the provider might need.</del></li> </ul> <h3 id="discussion">Discussion</h3> <p>This will not make all solutions work out of the box and in certain cases that can be a good thing. For instance an ElevenLabs TextToSpeech would require you to take a choice of the voice you want to use. We can set the requirement that required values have to have a default value, but in the case that you use ElevenLabs you 99% of the cases want to take a choice here.</p> <p>In a future where this is the default value for any audiotory discussion bot for producing website via spoken communication, we can of course have a default configuration exposes, much like we will have a default provider from the get go.</p>