Open webmaster128 opened 1 year ago
example for Telescope-generated objects
for decimal issues, we've added an option into Telescope
prototypes.typingsFormat.customTypes.useCosmosSDKDec
is the option, that will get embedded into decode
so RPC queries get fixed.
CosmJS made a few design decisions early on that are not great anymore. Part of the reason is that the protobuf API is getting more and more usable directly due to improvements in both Cosmos SDK and proto -> .ts code generation with Telescope. The other part is that the amount of messages and queries is getting a lot.
The group module alone adds 14 message types, more than all relevant modules combined when this was designed.
Instead of trying to catch up here, we should conceptually rething how those things should be done better.
Encode objects
We maintain types like
to combine the message type and the typeUrl in a type-safe way. We have 20 of them right now already but I am sure a lot of message types are missing
Amino converters
The
fromAmino
/toAmino
have to be written by hand (and ideally tested) for every message type supported.We have those types right now but not for all of them the converters are actually implemented:
Query wrappers
The extensible
QueryClient
is a nice idea in general, but someone has to write query wrappers for each query. Missing queries have been a source of frustration for users before. Also limited access to advanced setting like query height or pagination settings is an issue.