tauri-apps / tauri-apps/tauri-docs
[docs] Debug with jetbrains rust rover including front end
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 1.1k
- Forks
- 887
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 48
Description
I followed the docs here https://v2.tauri.app/develop/debug/rustrover/ but this does not include the front end for break points.
I am using the @tauri-apps/plugin-http' to fetch some data. When I debug according to the docs above none of my javascript breakpoints are hit but the fetch code runs fine in the tauri app. If I add a normal javascript debugging session for the default url of http://localhost:1420/ it opens a web page and my javascript break points are hit. However, because it is in the context of a webpage and not a tauri app the fetch code throws an invoke error.
How can I debug the javascript code that also invokes a call to rust with rustrover. TY
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the RustRover debugging documentation at https://v2.tauri.app/develop/debug/rustrover/ and reproduce the reported setup with the Tauri HTTP plugin. Document how frontend JavaScript breakpoints can be hit while the application still invokes Rust, and verify that the guidance covers the difference from debugging the default localhost page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust
- Domain
- devtools, documentation, frontend
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100