-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Symfony messenger support #62
Comments
Sorry for being late to the party 😄 I would really like to see that implemented or implement on my own but I am lacking a bit the uses cases.
|
@codedge sorry, forgot to reply 🙂
|
Sound good. I'll implement that, as it would make to usage of the package more attractive and open for more custom events per project/user with custom handlers. |
Awesome! |
@norkunas Just added a small fix to the current situation: You can now enable the The next thing is the Messenger integration. |
What about dispatching internal bundle event instead? |
I'd say by default listen on doctrine events and add an option to enable messenger :) |
96: Option to listen to postRemove event r=curquiza a=codedge This PR adds the option to listen to Doctrines `postRemove`. This is a result of the discussion in #62, a first step. You can know specify in `meili_search.yml`: ``` meili_search: # One, or multiple of postPersist, postUpdate, preRemove, postRemove doctrineSubscribedEvents: ['postPersist', 'postUpdate', 'preRemove', 'postRemove'] ``` @curquiza When merging this, we need to update the [wiki - Indexing automaticlly via ...](https://github.com/meilisearch/meilisearch-symfony/wiki/index-data-into-meilisearch#indexing-automatically-via-doctrine-events) Co-authored-by: Holger Lösken <[email protected]>
As the title says, it would be good if Symfony messenger would be supported out of the box :)
Currently we are using a custom message and a message handler, but there's a slight problem that it doesn't properly work for the document removal part from the index. To do a reall
->remove
call we use$objectManager->getReference()
.But then the call is delegated to
Engine
and calls$entity->getSearchableArray();
but as the entity is already removed, doctrine throws error that the entity not found because proxy tries to load it's information to normalize the searchable array.The text was updated successfully, but these errors were encountered: