Adding support for automation tools feature. #14
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Change “applicationName” from “Demo” to “”
Adding “build” command with options for supporting automation tools.
Adding “build” command usage. Change detailed to “Template for JSDoc 3”.
Adding folder for “build” command to use as default workspace.
|
👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding "build" command for supporting automation tools like Continuous Integration. It has its own default workspace like in /demo.
You can provide it (source files, destination files, config file) with the parameters for your own script like this.
By combine
gruntoption--gruntfilewith this 'build' command. It can make more ways to do with this JSDoc template.P.S. I also edit README.md file for better understanding and the example usage for 'build' command.