tauri-apps / tauri-apps/tauri-docs
[request] in v2 docs, it's hard to find the path to specific config field
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 1.1k
- Forks
- 887
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 48
Description
Question you want answered
How do I find the absolute path to config field in tauri.conf.json
Where did you look for an answer?
For instance it's not clear where should I place config/#nsisconfig inside tauri.conf.json.
I think the docs should somehow describe on each config field what's the absolute config path to that field and where to add it exactly inside tauri.conf.json
Page URL
https://v2.tauri.app/reference/config
Additional context
No response
Are you willing to work on this yourself?
- I want to work on this myself
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 at the v2 config reference page linked in the issue, especially the nsisconfig section, and inspect how configuration fields are documented in the repository. Determine where absolute paths should be shown for fields in tauri.conf.json and whether the convention can be applied consistently. Done means the relevant config documentation explains where each field belongs, including nsisconfig.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100