Fluid container loader providing core container loading functionality for the Fluid Framework
{
"context": "Evaluates how well the solution uses @fluidframework/container-loader lifecycle helpers to create, attach, load, and resume collaborative containers. Focus is on correct Loader wiring plus the specific creation/loading/rehydration helpers tied to container lifecycle.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Loader setup",
"description": "Constructs a @fluidframework/container-loader Loader with the provided urlResolver, documentServiceFactory, codeLoader, and options/logger so the same Loader instance drives all lifecycle calls.",
"max_score": 20
},
{
"name": "Detached attach",
"description": "Uses createDetachedContainer (via the package helpers) to build a new container and attaches it once to produce the resolved document URL requested by createAndAttach.",
"max_score": 25
},
{
"name": "Seeded creation",
"description": "When initial serialized state is supplied, bootstraps the container from that state using the package's rehydration path (e.g., rehydrateDetachedContainer) before attach instead of ignoring the snapshot.",
"max_score": 15
},
{
"name": "Existing load",
"description": "Opens previously attached documents by calling loadExistingContainer with the provided URL/resolver and returns the connected container without re-attaching.",
"max_score": 20
},
{
"name": "Pending resume",
"description": "Restores from serialized pending local state using the package's rehydration helper (rehydrateDetachedContainer or equivalent) so in-flight ops are preserved when connecting to the given document URL.",
"max_score": 20
}
]
}tessl i tessl/npm-fluidframework--container-loader@2.60.0evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10