Skip to content

test(e2e): register fixtures with visibility=0 (private) #133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ottovlotto merged 1 commit into from
May 6, 2026
Merged

test(e2e): register fixtures with visibility=0 (private) #133

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions tools/register-e2e-fixtures.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,11 @@
* alongside the new per-cell deploy domains added in Phase 3 (foundry, cdm,
* hardhat, multi).
*
* All fixtures are registered with `visibility = 0` (private) so they don't
* clutter the public playground.dot grid. The CLI tests that hit these
* domains use direct `getMetadataUri` queries (`dot mod <domain>`,
* registry-readback assertions), which are unaffected by visibility.
*
* Usage:
* bun tools/register-e2e-fixtures.ts # register all 5
* bun tools/register-e2e-fixtures.ts --domain e2efnd00 # one only
Expand Down Expand Up @@ -125,6 +130,7 @@ async function registerOne(fixture: Fixture, signer: Awaited<ReturnType<typeof r
domain: fixture.domain,
publishSigner: signer,
repositoryUrl: fixture.repositoryUrl,
isPrivate: true,
onLogEvent: (event) => {
if (event.kind === "info") console.log(` • ${event.message}`);
},
Expand Down
Loading