evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
{
"context": "Evaluates whether the solution builds and uses the notion-client NotionAPI correctly for authenticated workspace access with configurable base URL, time zone, and request overrides. Scoring focuses solely on how package APIs are invoked to honor defaults versus per-call options when fetching a page.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Auth config",
"description": "Uses notion-client's NotionAPI constructor with provided authToken and optional activeUser rather than hand-rolled headers.",
"max_score": 25
},
{
"name": "Base URL",
"description": "Passes apiBaseUrl into the NotionAPI options and forwards any per-call apiBaseUrl override when invoking getPage/getPageRaw or fetch instead of concatenating URLs manually.",
"max_score": 20
},
{
"name": "Time zone",
"description": "Supplies a default timezone to the NotionAPI configuration and allows per-call timeZone overrides to flow into getPage/getPageRaw requests without losing the default for later calls.",
"max_score": 20
},
{
"name": "Fetch options",
"description": "Provides fetchOptions/ofetchOptions to the NotionAPI constructor and merges per-call overrides when calling getPage or fetch, leaving stored defaults intact.",
"max_score": 15
},
{
"name": "Library fetch",
"description": "Uses the package's page retrieval methods (getPage or getPageRaw with supporting calls) instead of custom HTTP clients to honor the configured options.",
"max_score": 20
}
]
}