Fix Both IndexEntity & RemoveEntity messages are handled#67
Fix Both IndexEntity & RemoveEntity messages are handled#67loevgaard merged 1 commit intoSetono:masterfrom
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #67 +/- ##
============================================
- Coverage 33.36% 33.33% -0.04%
- Complexity 648 649 +1
============================================
Files 123 123
Lines 2161 2163 +2
============================================
Hits 721 721
- Misses 1440 1442 +2 ☔ View full report in Codecov by Sentry. |
|
I propose to not have the |
|
Ok for this! |
|
will you try and fix it or should I? :) |
|
I try to fix it today! |
|
Great, thanks :D |
4f7da24 to
68079c6
Compare
|
@loevgaard i add an I notice another issue (in the master branch) with |
| } | ||
|
|
||
| public function __invoke(RemoveEntity|IndexEntity $message): void | ||
| protected function handle(RemoveEntity|IndexEntity $message): void |
There was a problem hiding this comment.
| protected function handle(RemoveEntity|IndexEntity $message): void | |
| protected function handle(RemoveEntity|IndexEntity $message, callable $action): void |
I think I would change the signature to this and add the callback in the concrete handler like:
$this->handle($message, fn(Index $index) => $index->indexer()->removeEntity($entity););Wdyt?
68079c6 to
a7c27df
Compare
|
Great work, @SebLours 🎉 |
Fix #66