mirror of
https://github.com/fleetdm/fleet
synced 2026-05-23 08:58:41 +00:00
Clean up docs for generate (#11687)
Just some small copy improvements Co-authored-by: Jacob Shandling <jacob@fleetdm.com>
This commit is contained in:
parent
5fb37bff17
commit
31f8ecb489
1 changed files with 9 additions and 5 deletions
|
|
@ -1,6 +1,9 @@
|
|||
# Using `generate` to create boilerplate for a new Fleet UI component
|
||||
# Automatically generating UI component boilerplate
|
||||
|
||||
## Basic steps to create a new UI component
|
||||
Instead of manually creating each file, you can use
|
||||
the `generate` utility to automatically create the common boilerplate for a new Fleet UI component.
|
||||
|
||||
## Basic steps
|
||||
|
||||
1. `cd` into `fleet/frontend/components`
|
||||
2. Run `./generate -n NewComponentName`, replacing `NewComponentName` with the desired name for your
|
||||
|
|
@ -8,7 +11,8 @@
|
|||
3. A directory and all boilerplate for the various files of the component will be generated in
|
||||
`fleet/frontend/components`
|
||||
|
||||
You can also run `./generate -h` for information about the other options available (overwrite and
|
||||
specifying destination)
|
||||
|
||||
<meta name="pageOrderInSection" value="450">
|
||||
You can also run `./generate -h` for information about the other options available, overwrite and
|
||||
specifying destination.
|
||||
|
||||
<meta name="pageOrderInSection" value="450">
|
||||
Loading…
Reference in a new issue