[MGNLPER-31] Introduce a mechanism which communicates to all SearchResultSupplier Created: 29/May/18  Updated: 06/Feb/19  Resolved: 23/Jan/19

Status: Closed
Project: Periscope
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1

Type: Improvement Priority: Neutral
Reporter: Ilgun Ilgun Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: Periscope improvements
Story Points: 5

 Description   

This component should be aware of SearchResultSupplier and also should be responsible to handle communication to each SearchResultSupplier as well as filtering if needed. It also should be with convenient API which should be taking care of doing the search and delegate the job to the SearchResultSupplier individually.

Acceptance Criteria:

  • Filter results or SearchResultSuppliers by predicates
  • Provide API to ease search via SearchResultSuppliers
  • Replace for each SearchResultSupplier loops with the new component API

Generated at Mon Feb 12 10:28:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.