Improve Debugging: Use a tracing web-assembly adapter for the rust-client
- Lingua principale
- TypeScript
- Stelle
- 1
- Fork
- 21
- Merge medio
- 12h 14m
- PR unite (30g)
- 41
Descrizione
## Description
Debugging web-assembly errors can be hard with some errores being hard to make sense of.
We can make this easier through log statements in the code. We already have the tracing crate which provides the info!, debug! etc. family of macros for logging. We can also rely on this if we use one of these 3 adapters.
1. https://github.com/old-storyai/tracing-wasm
2. https://docs.rs/tracing-web/latest/tracing_web/
3. https://docs.rs/wasm-tracing/2.1.0/wasm_tracing/
1 & 2 are recommended in the tracing crate docs, but they seem a bit old, number 3 is an up-to-date fork
of 1. There might be other, better options around, so it's worth it to research it a bit before fully
committing to a specific crate.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Look at the rust-client code to see how tracing macros are currently used. Research the three listed crates (tracing-wasm, tracing-web, wasm-tracing) and any newer alternatives for compatibility with the project's wasm target. The goal is to integrate a tracing adapter so logs appear in the browser console. Test the integration by building the wasm output and checking debug output in a web environment.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- rust, typescript, wasm
- Ambito
- devtools, web-dev
- Tipo di issue
- Funzionalità
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 45/100