Added embedding generation. Avoid creating an instance of EmbeddingFieldFactory manually#3080
Added embedding generation. Avoid creating an instance of EmbeddingFieldFactory manually#3080
Conversation
…eldFactory manually
Preview of modified filesPreview of modified Markdown: |
code_samples/ change report
|
|
| 0.1111, | ||
| ]; | ||
|
|
||
| $embeddingProvider = $this->embeddingProviderResolver->resolve(); |
There was a problem hiding this comment.
With the vector defined in line 45 and embedding generated by the provider there are two contradicting ways of getting the vector. But vector is not used anymore in the command, so... how about I remove it completely?
There was a problem hiding this comment.
Also, what if the command example called the service to perform the searchByEmbedding function?
This way both the command and the service could stay in the example - the command would show how to obtain the embedding and call the service to find it, the service would call the query?
But... where would I want to put the filtering - command or the service? I guess the service?
| use Ibexa\Contracts\Taxonomy\Search\Query\Value\TaxonomyEmbedding; | ||
|
|
||
| final class TaxonomyEmbeddingSearchService | ||
| final readonly class TaxonomyEmbeddingSearchService |
There was a problem hiding this comment.
You suggested removing the service altogether - do you think I should keep it?
How about the two samples stay but i change their order, so that the service is presented first and then...
The command shows how it can be used?



No description provided.