Improve CLI docs (#1404)
* Improve CLI docs * Fixed all the typos (hopefully). * Improved the bad English. This encompasses grammar, vocabulary, generally awkward phrases, etc. The result is easier to read and understand, and in some cases shorter. * Made some formatting improvements. This includes making formatting more consistent, but I changed some of it to be better, at least in my opinion. * Removed certain unnecessities, the biggest one being the commands documentation. I think this is unnecessary because of the `dx --help` command. It also needs to be updated every time a command gets added/updated/removed. It doesn't really provide much extra insight than `dx --help`. * Improved plugin documentation. I added a warning to ignore all of it, which is ironic, but the fact is that plugins are probably going to change. But by the time I learned that, I already made some changes to the plugin docs. This includes a better guide on how to get started (although still bad since the plugin system is too messy), and some general changes like the aforementioned English or formatting. * And more. I can't list it all, but I didn't use any destructive changes. The content might be reformatted (to be shorter or easier to understand), but the meaning isn't lost. * Fix grammar in packages/cli/docs/src/creating.md Co-authored-by: Evan Simkowitz <esimkowitz@users.noreply.github.com> * Update README.md * Change config example --------- Co-authored-by: Evan Simkowitz <esimkowitz@users.noreply.github.com>
This commit is contained in:
1 parent
a0d1e5de3a
commit
94f76946fc
20 files changed
+308
-488
No files matched your search
@@ -1,10 +1,13 @@
|
||||
# Path Functions
|
||||
|
||||
> you can use path functions to operate valid path string
|
||||
You can use path functions to perform operations on valid path strings.
|
||||
|
||||
### join(path: string, extra: string) -> string
|
||||
### `join(path: string, extra: string) -> string`
|
||||
|
||||
This function can help you extend a path, you can extend any path, dirname or filename.
|
||||
<!-- TODO: Add specifics.
|
||||
From the example given, it seems like it just creates a subdirectory path.
|
||||
What would it do when "extending" file paths? -->
|
||||
Extend a path; you can extend both directory and file paths.
|
||||
|
||||
```lua
|
||||
local current_path = "~/hello/dioxus"
|
||||
@@ -12,9 +15,9 @@ local new_path = plugin.path.join(current_path, "world")
|
||||
-- new_path = "~/hello/dioxus/world"
|
||||
```
|
||||
|
||||
### parent(path: string) -> string
|
||||
### `parent(path: string) -> string`
|
||||
|
||||
This function will return `path` parent-path string, back to the parent.
|
||||
Return the parent path of the specified path. The parent path is always a directory.
|
||||
|
||||
```lua
|
||||
local current_path = "~/hello/dioxus"
|
||||
@@ -22,14 +25,14 @@ local new_path = plugin.path.parent(current_path)
|
||||
-- new_path = "~/hello/"
|
||||
```
|
||||
|
||||
### exists(path: string) -> boolean
|
||||
### `exists(path: string) -> boolean`
|
||||
|
||||
This function can check some path (dir & file) is exists.
|
||||
Check if the specified path exists, as either a file or a directory.
|
||||
|
||||
### is_file(path: string) -> boolean
|
||||
### `is_file(path: string) -> boolean`
|
||||
|
||||
This function can check some path is a exist file.
|
||||
Check if the specified path is a file.
|
||||
|
||||
### is_dir(path: string) -> boolean
|
||||
### `is_dir(path: string) -> boolean`
|
||||
|
||||
This function can check some path is a exist dir.
|
||||
Check if the specified path is a directory.
|
||||
Reference in new issue
Block a user