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 session description handling capabilities to implement a complete offer-answer exchange.",
"type": "weighted_checklist",
"checklist": [
{
"name": "createOffer usage",
"description": "Uses pc.createOffer() method to generate the WebRTC offer",
"max_score": 20
},
{
"name": "setLocalDescription call",
"description": "Calls pc.setLocalDescription() to set the created offer as the local description",
"max_score": 30
},
{
"name": "Plain object handling",
"description": "Passes the answerData parameter as a plain JavaScript object directly to setRemoteDescription() without manually constructing new RTCSessionDescription(), leveraging webrtc-adapter's automatic wrapping capability",
"max_score": 35
},
{
"name": "setRemoteDescription call",
"description": "Calls pc.setRemoteDescription() with the answer data to set the remote description",
"max_score": 10
},
{
"name": "Returns SDP string",
"description": "Returns the offer's SDP string (accessible via the offer object's sdp property or pc.localDescription.sdp) so it can be sent to the remote peer",
"max_score": 5
}
]
}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