| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
It looks like you removed the main readme ! please revert it .
there are unncessary files like .nojekyll , index.html etc in root. Please check.
please add tests as well
Sorry, something went wrong.
|
sorry about that! have no idea where those came from 👀 by tests do you mean adding a test to the ava snapshot e2e ? Thanks ! |
Sorry, something went wrong.
|
okay so I added tests but in order to do that I had to change the test structure a bit to accept command help. let me know what you think 🤘🏼 |
Sorry, something went wrong.
|
Thanks ! I will review it soon |
Sorry, something went wrong.
There was a problem hiding this comment.
Apologizes for the delay. Completely lost track of this.
Sorry, something went wrong.
| replace(target(filename), '_plugins_', '_plugin\n '.repeat(plugins.length)) | ||
| plugins.forEach(plugin => { | ||
| const major = version[0] | ||
| const url = plugin.includes('//') ? plugin : `https://cdn.jsdelivr.net/npm/docsify@${major}/lib/plugins/${plugin}.min.js` |
Sorry, something went wrong.
There was a problem hiding this comment.
I added the enquirer in #117, you can use this here as well.
Sorry, something went wrong.
There was a problem hiding this comment.
Ideally, we should support specifying a list of plugins as an argument to --plugins such that the prompt shows up on not supplying any or passing in an unsupported plugin.
docsify init [path] --plugins, -p [...plugins]
Sorry, something went wrong.
|
resolve #99 (comment) . When executing the init command, the user may not know which plugins he wants to use and the corresponding plugin names |
Sorry, something went wrong.
The success message should come after the prompt. |
Sorry, something went wrong.
Co-authored-by: James George <jamesgeorge998001@gmail.com>
done. |
Sorry, something went wrong.
|
@jamesgeorge007 Thank you for the modifications 790e96c But there seems to be some problems:
Initialization succeeded! Please run docsify serve docs-test/ |
Sorry, something went wrong.
|
Good catch. I've pushed a fix |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
having a go at #98 .
command: init
option: --plugins, -p
plugins are now supported via the following usage:
docsify init docs/ -p search gitalk <some_other_plugin>
note that by default a plugin will be added as a script tag with a url pointing to https://unpkg.com/docsify/lib/plugins/<plugin_name> otherwise it will use the url provided as an argument.
example and documentation was added to docs/README