SAK-52335 Search Refactor ECP events registrations and remove unused services#14363
SAK-52335 Search Refactor ECP events registrations and remove unused services#14363kunaljaykam wants to merge 1 commit intosakaiproject:masterfrom
Conversation
WalkthroughMultiple EntityContentProducer implementations now also implement EntityContentProducerEvents, replace per-event add/remove lists with centralized EVENT_ACTIONS/eventActions maps, always register with SearchIndexBuilder (remove SearchService gating), add getTriggerFunctions(), and update Spring bean wiring to use attribute refs and remove deprecated service properties. Changes
Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@coderabbitai full review |
✅ Actions performedFull review triggered. |
|
@kunaljaykam Is there any reason why we can't just merge EntityContentProducer and EntityContentProducerEvents? What is the logic behind having getTriggerFunctions as an optional piece? I would, personally, add a method called getTriggerEvents (I would remove the word Function as it implies the method returns some functions that can be applied elsewhere) to EntityContentProducer and just remove that extra interface from the existing content producers. You'd have to update the index builder pieces to call getTriggerEvents as well, obviously. However, maybe there's a good reason that getTriggerFunctions is in a separate interface? Seems weird to me. |
|
agreed functions is not a great name they're simply events that the service needs to fetch, also if the ECP registration needs to call this then it absolutely makes sense for this to not be a separate interface |
Summary by CodeRabbit