fixes #675 add pre-commit hook and apply it (#676)

Author: stevehu

.gitignore

@@ -20,4 +20,4 @@ bin/
 # virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
 hs_err_pid*
 
-**/.DS_Store
+**/.DS_Store

.pre-commit-config.yaml

@@ -0,0 +1,14 @@
+repos:
+-   repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v3.2.0
+    hooks:
+    -   id: trailing-whitespace
+    -   id: end-of-file-fixer
+    -   id: check-yaml
+    -   id: check-added-large-files
+-   repo: https://github.com/networknt/pre-commit-hook-keyword
+    rev: f17c4de14fc24420f6768c19cad06ba03af06d86
+    hooks:
+    -   id: keywordscan
+        args: ["--keywords=c3VubGlmZQ==,Y2liYw==,c3VuIGxpZmU="]
+        types: ["text"]

.travis.yml

@@ -4,7 +4,7 @@ cache:
     - $HOME/.m2
 jdk:
   - openjdk11
-  
+
 branches:
   only:
     - master

CONTRIBUTING.md

@@ -9,10 +9,10 @@ top of things.
 
 ## Core vs Modules
 
-New functionality is typically directed toward middleware components to provide 
-a slimmer Framework Core, reducing its surface area, and to allow greater freedom 
-for middleware developers and maintainers. 
- 
+New functionality is typically directed toward middleware components to provide
+a slimmer Framework Core, reducing its surface area, and to allow greater freedom
+for middleware developers and maintainers.
+
 If you are unsure of whether your contribution should be implemented as a
 middleware component or part of Framework Core, you may visit
 [Gitter Chat](https://gitter.im/networknt/light-4j) for advice.
@@ -44,7 +44,7 @@ middleware component or part of Framework Core, you may visit
 ### Documentation
 
 For changes of a trivial nature to comments and documentation, it is not
-necessary to create a new issue. 
+necessary to create a new issue.
 
 ### Example
 
@@ -55,12 +55,12 @@ Adding new examples or enhance examples won't need to create a new issue.
 
 * Push your changes to a topic branch in your fork of the repository.
 * Submit a pull request to the repository in the networknt organization.
-* The core team looks at Pull Requests on a regular basis and will merge the pull request. 
+* The core team looks at Pull Requests on a regular basis and will merge the pull request.
 * Sometimes, we might need to contact contributor understand the details of the pull request.
 
 # Additional Resources
 
 * [General GitHub documentation](https://help.github.com/)
 * [GitHub pull request documentation](https://help.github.com/send-pull-requests/)
 * [Light 4J Document](https://networknt.github.io/light-4j/)
-* [Light 4J Gitter](https://gitter.im/networknt/light-4j)
+* [Light 4J Gitter](https://gitter.im/networknt/light-4j)

README.md

@@ -10,14 +10,12 @@ A code generator based on [rocker](https://github.com/fizzed/rocker) that can be
 
 [![Build Status](https://travis-ci.org/networknt/light-codegen.svg?branch=master)](https://travis-ci.org/networknt/light-codegen)
 
-The Light platform contains several frameworks to build different styles of APIs or microservices based on the contract specifications. It encourages users to create service contract specification before coding, and it would be nice if we can scaffold a project based on the designed specification. Further, it would be even sweeter if we could utilize the specification during runtime to verify the security and validate input request/out response based on the same specification. 
+The Light platform contains several frameworks to build different styles of APIs or microservices based on the contract specifications. It encourages users to create service contract specification before coding, and it would be nice if we can scaffold a project based on the designed specification. Further, it would be even sweeter if we could utilize the specification during runtime to verify the security and validate input request/out response based on the same specification.
 
 Before we built our generator, we looked at the open-source community and couldn't find anything suitable for our needs. So we created one over a weekend, and it turned out very successful. If you want to know more about it, please check out the [light-codegen document](https://doc.networknt.com/tool/light-codegen/).
 
 The generator is very easy to use, and there are numeric ways to use it. Command-line, Docker, Scripting, and [Web UI](https://codegen.lightapi.net). To get started, please follow the [getting-started](https://doc.networknt.com/getting-started/light-codegen/).
 
 If you want to know all the options with the light-codegen, you can follow the tutorials for each generator at [light-codegen tutorial](https://doc.networknt.com/tutorial/generator/).
 
-Also, there are so many [other tutorials](https://doc.networknt.com/tutorial/) that are using light-codegen to scaffold projects, and these can be found in the tutorial section. 
-
-
+Also, there are so many [other tutorials](https://doc.networknt.com/tutorial/) that are using light-codegen to scaffold projects, and these can be found in the tutorial section.

codegen-cli/codegen.ps1

@@ -9,7 +9,7 @@ if (-not (Test-Path $cliJar)) {
     Exit 1
 }
 
-if (-not (Test-Path env:JAVA_HOME)) { 
+if (-not (Test-Path env:JAVA_HOME)) {
     Write-Host "JAVA_HOME is not set."
     Exit 1
 }

codegen-cli/codegen.sh

@@ -19,7 +19,7 @@ fi
 if [ ! -f "$CURRENT_DIR/rocker-compiler.conf" ]; then
     echo "generate config $CURRENT_DIR/rocker-compiler.conf"
 
-    echo "rocker.template.dir=$CURRENT_DIR" > rocker-compiler.conf 
+    echo "rocker.template.dir=$CURRENT_DIR" > rocker-compiler.conf
 fi
 
 if [ ! -d  "$CURRENT_DIR/target/classes" ]; then

codegen-cli/pom.xml

@@ -69,7 +69,7 @@
         <dependency>
             <groupId>com.fizzed</groupId>
             <artifactId>rocker-compiler</artifactId>
-        </dependency>        
+        </dependency>
         <dependency>
             <groupId>com.beust</groupId>
             <artifactId>jcommander</artifactId>

codegen-cli/src/main/java/com/networknt/codegen/Cli.java

@@ -148,4 +148,3 @@ public void run(JCommander jCommander) throws Exception {
     }
 
 }
-