linuxboot / linuxboot/contest

Chained target managers

Open
#22 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
20
Forks
17
PR merge metrics
No merged PRs in 30d

Description

Issue by insomniacslk
Monday May 11, 2020 at 15:19 GMT
Originally opened as https://github.com/facebookincubator/contest/issues/100


There are cases where a single target manager is not enough, and we may want to connect multiple target managers in a chain, to filter results. This requires a redesign of the target manager interface (to have multiple target managers) and in the way they are called in sequence, connecting the results of the previous to the next

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the target manager interface and the code that invokes it during result filtering. Read how a single manager currently receives and returns results; the work is done when multiple target managers can be connected in sequence and each manager receives the previous manager's results.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.