tauri-apps / tauri-apps/tauri-docs
[feature] Add a guide on default type conversions and workarounds between front and back
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- MDX
- Stars
- 1.1k
- Forks
- 887
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 48
Description
tatapstar:
Is it possible to add a guide on default type conversions and workarounds between front and back?
Simon:
Definitely, could you make a feature request for it on the tauri-docs repository so I don't forget about it? 🙂
context:
- I found problem: invoke command converts rust HashMap<i32, Node> to js/ts flat Array
Any solution? - https://github.com/tauri-apps/tauri/discussions/9153
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 invoke command conversion behavior described in the issue, especially Rust HashMap<i32, Node> becoming a JavaScript/TypeScript array, then read discussion #9153 for context. Done means the Tauri documentation includes default front-to-back type conversions and documented workarounds for the reported cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust, typescript
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100