livepeer / livepeer/livepeer-data
viewership: Differentiate between start and end views in Views API
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
In https://github.com/livepeer/livepeer-data/issues/51 it's listing startViews, needs to be differentiate in endViews, startViews and views as specified in https://www.notion.so/Expected-viewer-stats-out-of-MistServer-need-refinement-f8c1b8420b3e4be886a2c1d91062d2a5
Contributor guide
No contributing guide indexed for this repository
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 with the Views API and review the related issue at https://github.com/livepeer/livepeer-data/issues/51. Read the linked Notion specification to determine how endViews, startViews, and views should differ; the work is done when the API exposes those distinctions as specified and the relevant behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100