Persists the targets acquired by the TargetManager
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 20
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
_Thursday Feb 06, 2020 at 15:06 GMT_
_Originally opened as https://github.com/facebookincubator/contest/issues/34_
----
Right now there is no source of truth that tells which targets were acquired at the beginning of the job, that can be references for example at events submission time. To have a normalized data model, we need to store targets acquired as well.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the TargetManager and the event submission flow, then trace how acquired targets are currently represented. Define the normalized persistence path so targets acquired at job start remain available when events are submitted; the issue names no files or tests, so the exact completion checks must be established from the surrounding code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100