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 Feb 23, 2024. It is now read-only.
Hi, I am building on top of the Lens client/query library and am trying to add a type to search transactions (e.g. GetTxsEvent to start with).
It seems like the cosmos RPC library types, for example GetTxsEventResponse, do not automatically unpack their internal fields. For example, GetTxsEventResponse has internal Messages [] where each Message is the Any type. For my team's own use, we need to decode these Messages (among other fields in the GetTxsEventResponse).
My general thoughts on achieving this are:
The Lens ChainClientConfig needs to register the Modules e.g.
Then call e.g. tx.UnpackInterfaces(codec.InterfaceRegistry)
The question is: is the Lens team interested in this functionality being added as a PR (after I build out the TX library a bit more) and does the approach I discussed above make sense or is something better that I did not see included in the Lens or cosmos-sdk library.
The text was updated successfully, but these errors were encountered:
I believe the goal is to be able to use dynamic gRPC queries in the future which would allow dynamic initialization of the Msg types for a specific chain. I could be a bit off on this though.
Hi, I am building on top of the Lens client/query library and am trying to add a type to search transactions (e.g. GetTxsEvent to start with).
It seems like the cosmos RPC library types, for example
GetTxsEventResponse
, do not automatically unpack their internal fields. For example,GetTxsEventResponse
has internal Messages [] where each Message is theAny
type. For my team's own use, we need to decode these Messages (among other fields in theGetTxsEventResponse
).My general thoughts on achieving this are:
tx.UnpackInterfaces(codec.InterfaceRegistry)
The question is: is the Lens team interested in this functionality being added as a PR (after I build out the TX library a bit more) and does the approach I discussed above make sense or is something better that I did not see included in the Lens or cosmos-sdk library.
The text was updated successfully, but these errors were encountered: