evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
{
"context": "Evaluates how effectively the solution uses notion-client to fetch a full Notion page record map with optional hydration features and pagination controls.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Page fetch",
"description": "Instantiates NotionAPI and calls getPage as the primary retrieval method for the pageId instead of manual endpoints or raw fetches.",
"max_score": 25
},
{
"name": "Missing blocks option",
"description": "Maps includeMissingBlocks to fetchMissingBlocks in getPage options and returns hydrated child blocks when enabled, while avoiding the fetch when disabled.",
"max_score": 20
},
{
"name": "Collection hydration",
"description": "Maps includeCollections to fetchCollections in getPage options and surfaces collection/collection_view data from the returned ExtendedRecordMap when requested, disabling collection fetching otherwise.",
"max_score": 20
},
{
"name": "Signed files",
"description": "Enables signFileUrls in getPage when includeSignedFiles is true and propagates signed_urls from the ExtendedRecordMap; keeps signing off when not requested.",
"max_score": 20
},
{
"name": "Pagination controls",
"description": "Passes chunkLimit and chunkNumber through to getPage options to honor pagination/partial retrieval requirements.",
"max_score": 15
}
]
}