-
Notifications
You must be signed in to change notification settings - Fork 144
Added some docs on plugins. #500
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
base: main
Are you sure you want to change the base?
Conversation
Once that is setup, locate the folder `feather/quill/cargo_quill` in a terminal. Then run the following command. | ||
|
||
```bash | ||
cargo install --path <path to quill> |
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.
What is <path to quill>
? Do I need to build cargo-quill first?
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.
Yes, If i change it to cargo-quill, does that spark joy?
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.
I'm just not sure why you're using a placeholder. You could say "In the root directory of feather, run the following command" followed by cargo install --path quill/cargo_quill/
or you could also say "Navigate into quill/cargo_quill and run the following command", followed by cargo install --path .
.
I've submitted some wording changes, nothing too major. What's missing for me as an outsider is what the plugin should look like after I create it with cargo-quill (to see if I made a mistake or not) and what the general structure of a plugin is ( |
Co-authored-by: Tim Kt <[email protected]>
Co-authored-by: Tim Kt <[email protected]>
Co-authored-by: Tim Kt <[email protected]>
Co-authored-by: Tim Kt <[email protected]>
|
Started on docs for plugins with help from @Tracreed .