Add the ability to specify `{record: true}` on transcodes
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the CLI option parsing for the proposed --record flag and the transcode request path. Confirm how the {record: true} setting should be passed, add coverage for enabling it, and verify existing transcodes remain unchanged.
Written by the indexing model from the issue text.
Description
Probably with a --record CLI option.
- Dominant language
- Go
- Stars
- 9
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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.
More from livepeer/transcode-cli
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
livepeer/transcode-cli#10 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement
livepeer/transcode-cli#7 · 2 assignees ·
All issues in livepeer/transcode-cli
Similar issues
-
textual definition
Difficulty 1/5 Under an hour Newbie friendliness 90/100
geneontology/go-ontology#32653 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
needs design
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Priority/High ready-for-agent Severity/Major Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100