Repository navigation
docs: introduce Rust Developer SDK setup - #53
Conversation
edo-chan
left a comment
There was a problem hiding this comment.
The Rust setup pins a0eea63, but that commit is not an ancestor of the current Rust SDK #60 head (8d5e773). The current tip differs across 122 SDK source files, so the cited snippet compilation does not validate the code this docs stack is meant to describe. Before marking this chain ready, pin the intended final SDK revision and recompile the Rust snippets in #53–#58 against that exact revision. Mintlify validation and link checks pass at the docs tip, but they do not check Rust API compatibility.
abbb63d to
8943f97
Compare
8943f97 to
c3e8374
Compare
| <Tab title="Rust"> | ||
|
|
||
| ```bash | ||
| cargo add swig-developer-sdk@0.1.0 |
There was a problem hiding this comment.
[P2] Publish the crate before documenting this installation command
cargo +1.87.0 info swig-developer-sdk@0.1.0 currently fails with could not find swig-developer-sdk@0.1.0 in registry, so a new Rust user cannot get past the documented installation step. Please publish and verify version 0.1.0 before deploying these docs, or document a working pinned Git installation until the crate is available. The same crates.io instruction in developer-sdk/integration-paths.mdx needs to stay consistent.
Summary
Add native Rust SDK setup guidance alongside TypeScript and Python.
Changes
Pages updated
Validation
cargo +1.87.0 check --offline --lockedin a temporary harness. Application-owned inputs and callbacks are supplied by the harness.git diff --checkpasses.Stack
1 of 6 — Setup and configuration.
Base:
mainNext:
wuh/rust-docs-wallet-reads(#54)