2022-05-13 Developer Tools Update

[austinbaggio]

The developer tools team focuses on NEAR's tools, APIs, & SDKs for both Rust and Javascript.

Tools Feedback

You can reach out to Austin Baggio (Tools Product Manager) to share any feedback about this update or your experience using any of our Dev Tools:
30m Calendly Timeslot | austin.baggio@near.org | Discord | Twitter

Updates

near-sdk-js

• @itegulov, @volovyk-s & @ailisp are working on translating SDK-RS examples for the SDK-JS https://github.com/near/near-sdk-js/tree/master/examples
• @volovyk-s Improved the developer onboarding experience by fixing build scripts and READMEs (PR1)(PR2)
• @ailisp re-implemented nearbindgen to allow recursive @call @view methods
• @ailisp fixed the issue where storage write didn't work correctly after jsvm_call (cross contract call)
• @ailisp Enhanced the on jsvmCall API that encodes arguments and decodes the return for the developer
• @ailisp fixed 6 high level APIs (ecrecover/jsvmStorageRead etc.) that use low-level function returns, BigUint64 (JS BigInt), instead of Number.

workspaces-rs

• 🎉 0.3.0 version released (includes betanet support and updated protocol changes for sandbox) chore: bump workspaces patch version and update changelog near-workspaces-rs#136
• @ChaoticTempest started adding error types to allow users to handle specific errors in workspaces-rs
• @ChaoticTempest created the initial draft of what binary version management would look like in both workspaces and sandbox https://hackmd.io/@ChaoticTempest/SkBjQMw85
• @ChaoticTempest exposed raw_bytes API chore: expose raw_bytes API near-workspaces-rs#133
• @ChaoticTempest added more convenient methods to SecretKey type: chore: add secret key creation methods and added new KeyType type near-workspaces-rs#139
• @austinabell Updated default sandbox version for workspaces chore: bump sandbox version default for SDK change near-workspaces-rs#134
• @austinabell Added check for sandbox initialization to prevent potential bugs fix: error if sandbox process has already started near-workspaces-rs#135

near-cli (JS CLI)

• @ChaoticTempest is scoping the JS CLI commands needed to interact with JavaScript contracts

ABI

• @itegulov is working on a Rust ABI codegen library, it can already generate valid contract method cascades but actual RPC calls inside is still WIP

jsonrpc-client

• @miraclx fixed UnknownBlock variant parsing. fix: unserialized error compat is exclusively for .error_struct, not .data near-jsonrpc-client-rs#94
• @miraclx added logging, making the client's request / response payloads inspectable. feat: add logging near-jsonrpc-client-rs#97
• @miraclx Extended the create account example showing how to create sub-accounts & top-level accounts. https://github.com/near/near-jsonrpc-client-rs/blob/master/examples/create_account.rs
• @miraclx Reworked the JsonRpcError::handler_error method. fix: rework the JsonRpcError::handler_error method near-jsonrpc-client-rs#99

nearcore

• @miraclx is working through dependencies while updating actix-web to stable. It needs more investigation into migration changeshttps://github.com/chore: upgrade actix-web to v4.0.1 nearcore#6694
• @miraclx is working on releasing a new version (0.13.0) of public nearcore crates.

near-sdk-rs

• @austinabell
  Release 4.0.0-pre.9 of SDK chore: release pre.9 version near-sdk-rs#814
• Updated cross-contract call API change merged feat: refactor ext API and add new NEP264 functionality near-sdk-rs#742

[miraclx]

@thisisjoshford

• fixed UnknownBlock variant parsing. fix: unserialized error compat is exclusively for .error_struct, not .data near-jsonrpc-client-rs#94

The context behind this is, since we reuse the same structures as the server, we expect to be able to deserialize whatever the server serialized.

However, there are some cases where the server skips the serialization of some fields (near/near-jsonrpc-client-rs#28). Making it impossible to deserialize on the client side.

A patch was applied (near/near-jsonrpc-client-rs#29) to mitigate that, but that incorrectly treats the legacy, string-typed .data field as a JSON object, instead of the more appropriate .error_struct field from the server response.