Harry Solovay
Harry Solovay
I don't think we should get in the habit of overloading rune factories. Account IDs are more commonly used on chain for things such as keying into user-specific map entries...
I could see a world in which we have another static method / factory of `MultisigRune` that accepts the addresses for signatories. ```diff - const multisig = MultisigRune.from(westend, { signatories:...
Will pick up once asset conversion / dex pallet is included in at least one of the Polkadot devnet runtimes.
Yea, this is currently an issue. Somewhat described by #706, we ultimately decided that we would solve via #517. One could `.apply(onProxiesCreated, (...args) => {})` to hook into a comprehensive...
It doesn't: we can have a Rune factory that accepts non-runes such as fns. But I'm not so sure we should. Progress/event-tracking is something we should generalize in the Rune...
What might the API look like for pattern lib devs to mark a given rune in their tree as should-be-emitted?
Yea, let's rename + add it to #1077
For context: this will serve as a means of DI in Runes (for instance, injecting a custom logger, or runtime client)... perhaps a rune-ified paritytech/zones#20 (although may have a very...
Perhaps our DI approach can satisfy the use case of #706: consumers of pattern libs could hook into parts of the pattern's execution at pattern-dev-defined waypoints.
Idea for this feature: ```ts // 1. Define a key, to be used for applying to the placeholder. const userId = Symbol() // 2. Define a rune containing a placeholder(s)...