[Docs] Missing Rust code examples in Accounts quickstart page
- Lenguaje dominante
- TypeScript
- Estrellas
- 10
- Forks
- 50
- Merge medio
- 22 d 23 h
- PR fusionados (30 d)
- 1
Descripción
## Summary
The Accounts quickstart page (`docs/builder/quick-start/accounts.md`) provides Rust environment setup instructions but then only includes TypeScript code examples, leaving Rust developers with a dead end.
## Problem
The page instructs Rust users to set up their environment:
```bash
touch src/bin/demo.rs
cargo run --bin demo --release
```
It then presents tabbed code examples (TypeScript/Rust) for "Creating Accounts Programmatically" and "Creating a Token Faucet." However, the Rust tab appears to be empty or missing actual code, while the TypeScript tab has complete working examples.
A developer following the Rust path would:
1. Set up their Rust binary as instructed
2. Click the "Rust" tab for the code example
3. Find no code to put in the file they just created
## Suggested Fix
Add complete Rust code examples for the "Creating Accounts Programmatically" and "Creating a Token Faucet" sections, matching the pattern already used in the Notes & Transactions page (`notes.md`) which does include full Rust examples using `AccountBuilder`, `ClientBuilder`, etc.
The Rust examples in `notes.md` (mint.rs, consume.rs, send.rs) already demonstrate the same account creation flow and could serve as a reference for the missing code.
Guía de contribución
Línea de trabajo
Examine the existing Rust examples in docs/builder/quick-start/notes.md (mint.rs, consume.rs, send.rs) to understand the pattern using AccountBuilder and ClientBuilder. Then, update the accounts.md file to add the missing Rust code snippets for 'Creating Accounts Programmatically' and 'Creating a Token Faucet' sections, ensuring they match the TypeScript examples in structure and functionality. Verify the changes by building the documentation locally.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- rust
- Área
- documentation
- Tipo de issue
- Documentación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Estado de actividad
- Estancado
- Claridad
- Bien especificado
- Aptitud para principiantes
- 70/100