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
The subxt macro currently supports to fetch the metadata from the filesystem or from some RPC node. However, for the future zombienet rust tests, it would be nice to also specify a crate.
So, something like this:
subxt(runtime_crate = "crate_name", wasm_file_name = "name", features = ["fast-runtime"])
The crate_name would be required to be path of the same workspace. wasm_file_name should be optional and if not given, it should be guessed based on the build output. If there is more than one wasm file, the macro should complain. features is also optional and just activates some feature at compile time.
From the linked issue, I like the idea that you can point Subxt at the WASM runtime and have it extract and use the metadata from it. Then, I think we could have:
runtime_metadata_path - get metadata from path
runtime_metadata_insecure_url - get metadata from (possibly not secure) URL
runtime_path - get metadata from runtime at path
I'd prefer to avoid the subxt macro having to know or care anything about the structure of the polkadot-sdk repo if possible :)
The
subxt
macro currently supports to fetch the metadata from the filesystem or from some RPC node. However, for the future zombienet rust tests, it would be nice to also specify a crate.So, something like this:
The
crate_name
would be required to be path of the same workspace.wasm_file_name
should be optional and if not given, it should be guessed based on the build output. If there is more than one wasm file, the macro should complain.features
is also optional and just activates some feature at compile time.https://github.com/paritytech/polkadot-sdk/tree/85f0edae1d6c461081f42fcabd13e547e5a5b683/substrate/.maintain/build-only-wasm.sh could be helpful here.
The text was updated successfully, but these errors were encountered: