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 client will not generate a query helper for it, rather just ignore it (unless i missed an option for it)
Tho it will recognize it as a type in the types file:
exporttypeQueryMsg="get_admin"|"get_config" ...
But that doesn't help much, as the general query of the SigningCosmWasmClient function doesn't know those types, so its not really giving me any type checks.
The preferred way for me:
To generate a simple helpers for those queries as well, will make it a lot easier to use.
Less preferred way
Generate a general query message specific to the schema, this at least will give us some type checks as the general query function will accept the contract specific QueryMsg and not just any.
Something like:
If we have a query like this:
The client will not generate a query helper for it, rather just ignore it (unless i missed an option for it)
Tho it will recognize it as a type in the types file:
But that doesn't help much, as the general query of the
SigningCosmWasmClient
function doesn't know those types, so its not really giving me any type checks.The preferred way for me:
To generate a simple helpers for those queries as well, will make it a lot easier to use.
Less preferred way
Generate a general query message specific to the schema, this at least will give us some type checks as the general query function will accept the contract specific
QueryMsg
and not justany
.Something like:
The text was updated successfully, but these errors were encountered: