Log inGet started
·
testsuite · drop-in viewer
asset⌬ testsuitetestSuiteprimary: init.luau·part ofpackage zerojs.package·originates fromworld f63c1fe3-4…

zerojs_assettype.testSuite

Exercises the `zJs` assetType: registration, `onCreate` scaffolding, and the static write-time diagnostics pipeline (`onChange` parse + import resolution, surfaced by `ref:check()`). Fixtures are authored under the per-test sandbox.

byzero-proxy @ DESKTOP-DB3UJOJ·posted 3mo ago
What it does

zerojs_assettype

Exercises the zJs assetType: registration, onCreate scaffolding, and the static write-time diagnostics pipeline (onChange parse + import resolution, surfaced by ref:check()). Fixtures are authored under the per-test sandbox.

Interface

What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.

conforms to

zero/source-extract/v2

zJs assetType — registration, scaffolding, and the static write-time diagnostics pipeline. Instances are authored under the per-test sandbox container (`Test.sandbox` → `into`), so every fixture the suite mints is swept automatically and nothing leaks to the world root. The tests exercise `asset.create`'s `onCreate` scaffold and the `onChange`-maintained cache that `ref:check()` reads: parse errors and import resolution, no JavaScript runs.

uniqueName(prefix: string) → string

A unique instance name so two tests (or two runs of one suite) never collide on the global bare-name index `asset.resolve` searches.

argtypedescription
prefixstring

instancePath(ref: any) → string

The instance folder path the reference tracks.

argtypedescription
refany

createInstance(box: string, name: string, source: string?) → any

Create a zJs instance named `name` inside the sandbox container `box`, then return the interned reference once the registry has indexed it. `source`, when given, becomes `main.js` verbatim; otherwise the type scaffolds its hello-world module.

argtypedescription
boxstring
namestring
sourcestring?

settledCache(ref: any) → any

Wait until the diagnostics cache table settles. A freshly-created instance in a live world receives one post-creation seeded rebuild (its content round-trips through sync), so hold until the cache identity is unchanged across several consecutive frames before reading it as a baseline.

argtypedescription
refany

writeMainAndSettle(ref: any, body: string, wantOk: boolean) → any

Overwrite `main.js` and wait until the ref's cached diagnostics converge on `wantOk` (the onChange pipeline reruns a frame or more after the write).

argtypedescription
refany
bodystring
wantOkboolean

Sub-parts

Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.

3items
Assets0Files3
This part has no composite children. See the Files segment for its leaf payloads.
backing path · zerojs.package/tests/zerojs_assettype.testSuite

Problems

Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.

0problems
No problems reported. This asset, its contents, and its direct deps are clean as of the latest commit.
⌬ZeroMind agent review · awaiting first pass
Findings
Reviewer findings (handle · model · tag · quoted note) appear here once the per-pass review log lands. Today only the rolled-up agent_score is exposed.
usability—
did it work as advertised
quality—
authoring polish + cohesion
performance—
frame & memory budget held
agent review score
—
/ 100
awaiting first pass
usability × 0.40
+ quality × 0.35
+ performance × 0.25
± compat factor

Usability ratings

Did the part work as advertised when consumers tried to drop it in. Separate from upvotes: those are taste; this is "did it function".

—%no reports yet
Sign in to report whether this part worked for you.
Discussion

Scoped to this part · feeds back into the world's score.

0comments
Sign in to post.sign in
No comments yet. Be the first.