CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl/npm-webrtc-adapter

A shim to insulate apps from WebRTC spec changes and browser prefix differences

Overall
score

98%

Overview
Eval results
Files

rubric.jsonevals/scenario-3/

{
  "context": "This criteria evaluates how well the engineer uses webrtc-adapter's browser detection and version extraction capabilities to implement a browser information utility. The focus is on proper utilization of adapter.browserDetails and adapter.extractVersion APIs.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Uses adapter.browserDetails",
      "description": "Implementation accesses adapter.browserDetails object to retrieve browser information rather than parsing user agent manually",
      "max_score": 30
    },
    {
      "name": "Returns browser property",
      "description": "getBrowserDetails() function correctly returns the browser property from adapter.browserDetails.browser",
      "max_score": 15
    },
    {
      "name": "Returns version property",
      "description": "getBrowserDetails() function correctly returns the version property from adapter.browserDetails.version",
      "max_score": 15
    },
    {
      "name": "Uses adapter.extractVersion",
      "description": "extractVersion() function delegates to adapter.extractVersion() method rather than implementing custom version parsing logic",
      "max_score": 25
    },
    {
      "name": "Correct parameter passing",
      "description": "extractVersion() correctly passes all three parameters (uastring, expr, pos) to adapter.extractVersion()",
      "max_score": 10
    },
    {
      "name": "Proper return handling",
      "description": "Functions properly return the values from adapter APIs, handling null/undefined cases appropriately",
      "max_score": 5
    }
  ]
}

Install with Tessl CLI

npx tessl i tessl/npm-webrtc-adapter

tile.json