func Count
ActionCount is how many tools the directory holds.
Package toolbox is the directory of moul's small gno.land utilities: one page listing every tool, each tool a realm o...
gno.land/r/moul/toolboxA home for small utilities on gno.land. One page listing every tool; each tool is its own
realm at r/moul/toolbox/<slug>.
A tool composes contracts that are already on chain and renders the answer, so you open a page instead of composing a query. The toolbox adds the view, not the data.
/r/moul/toolbox the directory
/r/moul/toolbox?tag=identity the directory, filtered to one tag
/r/moul/toolbox:usernames one tool
The obvious design is the opposite one: each tool calls Register on this realm from its own
init, and the directory assembles itself. That design is unavailable here, and the reason is
not a preference.
private = true buys redeploy-in-place at the same path and costs the ability to be imported:
the type checker refuses any realm importing a private one (ImportPrivateError). A private
hub therefore cannot be imported by its tools, and a hub that accepts registration has to be
public. A public realm can never be redeployed at its own path, so a public hub would be
frozen at v0 and the first bug in it would move the directory's URL.
A stable URL is the whole point of a directory, so the trade goes the other way: everything
here is private and redeployable, and adding a tool is one entry in tools plus a redeploy.
The catalog is rebuilt from source every time, so the redeploy wipe costs nothing. There is no
state to lose.
p/moul/toolbox's Catalog stays mutable for whoever
wants the other trade.
/vN/vN exists because a public path can never be redeployed, so a fix there means a new path.
This realm is private and redeployable, so its version could never increment and the suffix
would be a promise it cannot keep. The URL is the product here, bookmarked the way a blog post
is, so it is the one that should not carry it. unversionedContracts in
tools/gnocontracts/model.go is the allowlist, with the reason per entry.
One entry in tools, then redeploy. buildCatalog panics at deploy, not at read, if the slug
and the path disagree, so a copy-pasted entry that kept the wrong path fails the publish rather
than shipping a dead link.
Flat strings, because a nested value inside a persisted object prints as an opaque ref(...)
over vm/qeval:
1gnokey query vm/qeval -remote https://rpc.gno.land \
2 -data 'gno.land/r/moul/toolbox.Slugs()'
3gnokey query vm/qeval -remote https://rpc.gno.land \
4 -data 'gno.land/r/moul/toolbox.PathOf("usernames")'
Package toolbox is the directory of moul's small gno.land utilities: one page listing every tool, each tool a realm of its own at `r/moul/toolbox/<slug>`.
It holds no logic. A tool composes other contracts (resolve a username, read a DAO, decode a denom) and renders the answer; this realm only says which tools exist and where they are. The model, the rendering and the query-form builder are p/moul/toolbox(/p/moul/toolbox/v0).
The obvious design is the opposite one: each tool calls `Register` on this realm from its own init, and the directory assembles itself. That design is unavailable here, and the reason is worth stating because it is not a preference.
`private = true` buys redeploy-in-place at the same path and costs the ability to be imported: the type checker refuses any realm importing a private one (`ImportPrivateError`, `gnovm/pkg/gnolang/gotypecheck.go`). So a private hub cannot be imported by its tools, and a hub that accepts registration has to be public. A public realm can never be redeployed, which would freeze this path at v0 and move the directory's URL on the first bug in it.
A stable URL is the whole point of a directory, so the trade goes the other way: everything here is private and redeployable, and adding a tool is one entry in [tools] plus a redeploy. The catalog is rebuilt from source every time, so the redeploy wipe costs nothing: there is no state to lose.
p/moul/toolbox.Catalog stays mutable for whoever wants the other trade.
Count is how many tools the directory holds.
DescOf returns the one-line description of one tool, or "".
Has reports whether a tool with that slug is listed.
PathOf returns the package path of one tool, or "" when there is no such tool. Flat strings rather than the struct: a nested value inside a persisted object prints as an opaque `ref(...)` over `vm/qeval`, so a read API that is meant to be queried returns scalars.
1gnokey query vm/qeval -data 'gno.land/r/moul/toolbox.PathOf("usernames")'
Slugs lists every tool's slug, in directory order.
1gnokey query vm/qeval -data 'gno.land/r/moul/toolbox.Slugs()'
Tags lists every tag any tool carries, each once.
TitleOf returns the human name of one tool, or "".