or run

tessl search
Log in

Version

Files

tile.json

rubric.jsonevals/scenario-9/

{
  "context": "This criteria evaluates the engineer's proficiency in using @mdx-js/mdx's runtime execution capabilities, specifically the compile-then-execute workflow using run/runSync functions with function-body output format.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Function-body compilation",
      "description": "Uses compile() or compileSync() with outputFormat: 'function-body' option to generate code suitable for deferred execution",
      "max_score": 25
    },
    {
      "name": "Run function usage",
      "description": "Uses run() or runSync() functions to execute the pre-compiled code, correctly passing the compiled code as the first parameter",
      "max_score": 25
    },
    {
      "name": "JSX runtime provision",
      "description": "Provides the JSX runtime (jsx, jsxs, Fragment, or jsxDEV) in the options parameter when calling run/runSync, typically from 'react/jsx-runtime'",
      "max_score": 20
    },
    {
      "name": "Async/sync handling",
      "description": "Correctly implements both asynchronous (compile + run) and synchronous (compileSync + runSync) execution paths",
      "max_score": 15
    },
    {
      "name": "Module exports access",
      "description": "Correctly accesses the default export (component) and named exports from the module object returned by run/runSync",
      "max_score": 10
    },
    {
      "name": "Separation architecture",
      "description": "Properly separates compilation service from execution service, demonstrating the compile-once-execute-elsewhere pattern without using evaluate/evaluateSync",
      "max_score": 5
    }
  ]
}