-
Notifications
You must be signed in to change notification settings - Fork 659
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: create OS Information guide #1484 #1642
Conversation
✅ Deploy Preview for tauri-docs-starlight ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
To your point on this being a JS/Rust API reference I agree. I think that instead of listing out each different function, we could instead just have on function (such as |
Is that how you imagined? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would just move this link to be further up at the top so the reader can more easily see it.
Co-authored-by: Lorenzo Lewis <[email protected]>
Co-authored-by: Lorenzo Lewis <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! And good catch with the docs.rs link
What kind of changes does this PR include?
Description
I'm putting this out but I'm not sure what the Rust code, or even the JS should included, I mean, how much detail or step. Right now the Rust code is minimal, so is the JS, it's almost like the js-api reference. For comparison in the clipboard guide #1622, I've included three steps to use the Rust code, with the end goal of invoking in frontend.
edit: ok, I'm readin https://diataxis.fr/