You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 14, 2023. It is now read-only.
Let's say we're using a Capi pattern lib
multisig_util
.Let's use an import map to specify the chain.
import_map.json
What if we want to utilize this lib twice in the same file, with two different chains? Given this approach, we cannot.
On one hand, we could design libs such that the "compass" needs to be injected into instances at runtime.
But this is lackluster, as one does not get the type-checking against the target chain (not ideal).
I believe we'll need to tackle this via the codegen server (#471)
How would this look with the import-mapped lead?
I suppose any valid import spec could follow
/lib
(as well as anything defined within the import map)The text was updated successfully, but these errors were encountered: