Harry Solovay
Harry Solovay
Currently, specifying `--target` does not actually touch the codegen; it passes an env var, which is picked up by the `detectConnect` util. Although we could swap out the served chain...
Blocked on #517 **EDIT** Indeed @tjjfvi, I commented on the wrong issue. Ignore.
This is an interesting proposal; we will consider it and follow up here when we can.
I haven't attempted cancellation, but event extraction is seemingly working fine. ```ts import { polkadotDev } from "@capi/polkadot-dev" import { createDevUsers } from "capi" import { MultisigRune } from "capi/patterns/multisig"...
Or, a `signableRune` factory
Blocked on #517
Would it be possible for us to boil this into `Rune.array`, `Rune.tuple` and `Rune.rec` without too wild of typings? Aka. ```ts const a = Rune.constant(["a", "b", "c"]) const b =...
Having to tuple/record/array-ify some values in order to map them into their merged counterpart is... a lot. Is there another approach that would offer the same usability gain?
Regarding this... ```ts const merged = Rune.tuple([a.spread, 1, 2, 3, b.spread]) ``` ... it has the same problem as one of the aforementioned designs: in T6's words: > `The typings...
You can achieve this like so. ```ts import { chain } from "westend_dev/mod.js" const properties = await chain.connection .call("system_properties") .run() ``` You could also access this from the FRAME metadata...