fix(abstract-cosmos): add type guards to ContractCallBuilder message handling #8037
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
ContractCallBuilder.messages()method incorrectly casts all messages toMessageDatawithout type checking, causing potential runtime errors when handlingCosmosTransactionMessagetypes.Changes:
'typeUrl' in message && 'value' in message) before accessing MessageData propertiesExample:
This prevents runtime errors when messages don't conform to the MessageData shape, particularly when mixing typed messages with pre-encoded message formats in group proposals.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.