TECH - définir le déclencheur comme étant le crawler quand le usecase a été déclenché par lui #2302
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
celineung
force-pushed
the
fix-usecase-triggerdby-when-triggerdby-crawler
branch
from
0b5a5ae
to
17b73f6
Compare
|
Review app: |
JeromeBu
approved these changes
Oct 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problème
Lorsqu'un usecase a été déclenché par l'outbox, il n'a pas de
currentUserde défini.Or dans le usecase
UpdateAgencyReferringToUpdatedAgencyon cherchait à accéder à l'id de cecurrentUserqui est undefined. On obtenait finalement l'erreur:Solution
Définir le déclencheur comme étant le crawler quand le usecase a été déclenché par lui