fix: fixes issue #2653 Cannot decode DataContractCreateV1 with WASM-DPP#2654
Conversation
WalkthroughThe changes update methods for retrieving data contracts in WASM bindings to support protocol version awareness. Method signatures now accept an optional protocol version, use it to resolve the platform version, and return a Changes
Sequence Diagram(s)sequenceDiagram
participant JS as JavaScript
participant WASM as WASM Bindings
participant Platform as PlatformVersion
JS->>WASM: get_data_contract(protocol_version?)
WASM->>Platform: resolve PlatformVersion (from protocol_version or latest)
WASM->>WASM: try_from_serialization_format_with_platform_version(data, false, platform_version)
WASM-->>JS: Result<DataContractWasm, JsValue>
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (6)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Summary by CodeRabbit
New Features
Bug Fixes
Tests