-
Notifications
You must be signed in to change notification settings - Fork 689
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: autogenerate CLI command docs #2535
Conversation
✅ Deploy Preview for tauri-v2 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
New dependencies detected. Learn more about Socket for GitHub ↗︎
|
Due to pnpm/pnpm#7002 it's tricky to automatically update the CLI before generating docs.. I suggest we let renovate handle that for us for now. |
} | ||
|
||
function generateCommandDoc(command: string, level: number, subcommandList: Command[]): string { | ||
const output = execSync(`pnpm tauri ${command} --help`) |
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.
This approach is kinda fragile whenever we change the layout of the help output but I don't think that will happen more than once.
Also running the binary just for the help output sounds weird when we have access to the docs/source code itself since we have tauri as a git submodule.
Is tauri auto generating the rustdocs/scheme and we can consume them the same way we do for the permissions and configs? If not is it not feasible to do so?
No description provided.