Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Resource not dispatch when a data persister support it ?
See original GitHub issueHi, Is there a reason why a resource is dispatched (when using messenger property) only if there is no DataPersister which can handle this resource or is it some kind of conflict ?
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (9 by maintainers)
Top Results From Across the Web
Call child resource data persisters - symfony - Stack Overflow
I want to call the data persisters of all my child's entities from a parent entity. For example, the entity Demand has some...
Read more >Outbox • NServiceBus • Particular Docs
Most message queues, and some data stores, do not support distributed transactions. This may cause problems when message handlers modify business data.
Read more >Data Persister Decoration > API Platform Part 3 - SymfonyCasts
Ah! It's recursion! This means that the data persister must be passed via autowiring.
Read more >API Platform 2.4: MongoDB, Elasticsearch, Mercure, OpenAPI ...
To do so, you can use Logstash, a custom data persister or any ... It is natively supported by modern browsers (no required...
Read more >How To Use Redux Persist in React Native with Asyncstorage
This is not a good user experience. To improve this user experience, ... Since a Base URL is required to fetch the data,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Indeed, by changing the priority to a high value my resource is dispatched !
It seems like we have a priority issue. I suspect we should change the Messenger DataPersister to have a high priority (e.g. 1000), currently it’s -900. If the user needs a custom DataPersister when
messengerproperty is set to true, then they could use a higher priority, but that should be an edge case.