A shim to insulate apps from WebRTC spec changes and browser prefix differences
Overall
score
98%
{
"context": "This criteria evaluates how well the engineer uses webrtc-adapter's Legacy Stream API to implement a stream monitoring solution. The focus is exclusively on correct usage of getLocalStreams(), getRemoteStreams(), addStream(), and onaddstream event handling.",
"type": "weighted_checklist",
"checklist": [
{
"name": "getLocalStreams() usage",
"description": "Uses RTCPeerConnection.getLocalStreams() method to retrieve local streams from the peer connection",
"max_score": 25
},
{
"name": "getRemoteStreams() usage",
"description": "Uses RTCPeerConnection.getRemoteStreams() method to retrieve remote streams from the peer connection",
"max_score": 25
},
{
"name": "onaddstream event",
"description": "Sets up onaddstream event handler or uses addEventListener('addstream') to detect when remote streams are added to the connection",
"max_score": 30
},
{
"name": "Stream counting",
"description": "Correctly combines local and remote stream arrays to calculate total stream count using the results from getLocalStreams() and getRemoteStreams()",
"max_score": 20
}
]
}Install with Tessl CLI
npx tessl i tessl/npm-webrtc-adapterdocs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10