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
#394removes the lookup for error details from metadata at runtime, instead using the static metadata.
This will only work if the configuration of the target runtime modules is identical to that of the compile time metadata. So for tools which target a single pallet that might be present across many versions of many chains (e.g. cargo-contract, or xcm-cli) then the error resolution might not work.
This was one of the original design goals for this library, and indeed the resolution of indices for constructing extrinsics and decoding events is still dynamic. So there should also be a similar mechanism for resolving runtime error details.
The text was updated successfully, but these errors were encountered:
I guess the best option is to reinstate the dynamic error information fetching code that was removed in that PR. We could then ponder either removing the statically generated stuff and tweaking the API to obtain details from the dynamic again, or keep both.
#394 removes the lookup for error details from metadata at runtime, instead using the static metadata.
This will only work if the configuration of the target runtime modules is identical to that of the compile time metadata. So for tools which target a single pallet that might be present across many versions of many chains (e.g.
cargo-contract
, orxcm-cli
) then the error resolution might not work.This was one of the original design goals for this library, and indeed the resolution of indices for constructing extrinsics and decoding events is still dynamic. So there should also be a similar mechanism for resolving runtime error details.
The text was updated successfully, but these errors were encountered: