chore(cdm): sync playground-registry manifest to v3 (sorted-index reads)#273
Merged
Conversation
Regenerated with cdm 0.8.18 (cdm i -n paseo) against the live meta-registry (0xf62c2ece). Picks up the v3 redeploy of @w3s/playground-registry at 0x9938255f40485B25641C9bc263aa8E0bAE8c202d from playground-app PR #277, which adds the on-chain sorted-index read methods getTopStarred(start, count) / getTopModded(start, count) backing the Apps-tab most-starred / most-modded sorts. No existing method signatures changed. The whitespace churn is the generator's canonical 2-space JSON style (same as playground-app's manifest); future cdm i runs are zero-diff. Addresses keep resolving live from the meta-registry, so this snapshot only refreshes the ABI surface and the recorded version/address/CID.
Contributor
|
Dev build ready — try this branch: |
Contributor
E2E Test Pass · ✅ PASSTag:
Sentry traces: view spans for this run |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Regenerates the CDM snapshot with
cdm i -n paseo(cdm 0.8.18) against the live meta-registry (0xf62c2ece), picking up the v3 redeploy of@w3s/playground-registryat0x9938255f40485B25641C9bc263aa8E0bAE8c202dfrom playground-app PR #277.Why
playground-app added on-chain sorted indexes for the Apps-tab sorts and redeployed the registry. The new ABI surface:
getTopStarred(start, count)- apps ranked by star countgetTopModded(start, count)- apps ranked by mod countBoth return the same
AppsPageshape asgetApps. No existing method signatures changed, so no CLI code changes are needed; the typed contract handle simply gains the two new read methods.Notes
ContractManager.fromLiveClient+ the"latest"pin), so the snapshot only refreshes the ABI surface and the recorded version/address/metadataCid. Verified the CLI snapshot is now byte-identical (ABI deep-equal) to playground-app's manifest.cdm.json); futurecdm iruns are zero-diff. Biome does not cover root JSON, soformat:checkis unaffected..cdm/*.d.tstypings were regenerated too but are gitignored (local-only).Verification
pnpm format:checkpasspnpm lint:licensepasspnpm test579/579 passpnpm buildpass