Dashboard player indicates stream with no profiles configured still has transcoded renditions
- Dominant language
- TypeScript
- Stars
- 88
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug (required)** A clear and concise description of what the bug
is.
Related to #1146
When a stream is created in the API without any profiles by setting `profiles: []`, the dashboard player still indicates that there are transcoded renditions.
The result of GET /stream:
```
{
...
"profiles": [],
"createdAt": 1657228755876,
...
}
```
Here is a screenshot when the stream is active:

Notice that there are renditions that the player supports switching to.
**Expected behavior (required)** A clear and concise description of what you
expected to happen.
The dashboard player to display zero renditions when there are zero profiles configured for the stream.
**To Reproduce (required)** Steps to reproduce the behavior:
Create a stream with zero profiles (`profiles: []`) and watch the dashboard player when the stream is active.
Contributor guide
Research direction
Reproduce the issue in the dashboard player with an active stream created using profiles: []; the issue includes the relevant GET /stream response and screenshot. Inspect the dashboard player entry point that determines available renditions, and verify that the completed behavior displays zero renditions when the stream has no configured profiles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100