feat: convert to Angular CLI project structure for library and app (JsDaddy#588)

* feat: convert to Angular CLI project structure for library and app

* feat: update to npm 6.9.0 and use ci script for Travis

* feat: added helper scripts for npm pack and publish

* docs: update

* feat: copy the root readme and license to dist folder

* docs: update

* chore: doc updates

* test: updates

* chore: use prettier defaults for tab and semi colon

* chore: run prettier on all ts files

chore: a

* fix: use special characters that user has specified JsDaddy#580

* chore: up version

* chore: helper scripts for version updates and releasing

* chore: up version and changelog

* style: add bit of spacing and separate sections on the demo app

* chore: manual merge of develop

Author: ColinMorris83

.angulardoc.json

@@ -0,0 +1,5 @@
+{
+  "extends": [
+    "@commitlint/config-conventional"
+  ]
+}

.commitlintrc.json

@@ -39,3 +39,5 @@ Thumbs.db
 .ng_pkg_build/
 dist.tgz
 yarn.lock
+
+test-reports/

.gitignore

@@ -0,0 +1,8 @@
+{
+  "default": true,
+  "MD013": false,
+  "MD033": false,
+  "MD041": false,
+  "MD014": false,
+  "MD024": false
+}

.markdownlint.json

@@ -1,7 +1,5 @@
 {
-    "singleQuote": true,
-    "tabWidth": 4,
-    "semi": true,
-    "trailingComma": "es5",
-    "printWidth": 120
+  "singleQuote": true,
+  "trailingComma": "es5",
+  "printWidth": 120
 }

.npmignore

@@ -17,12 +17,8 @@ git:
   depth: 3
 
 before_install:
-  - npm install -g npm@~5.3.0
-
-install:
-  - npm install
+  - npm install -g npm@~6.9.0
 
 script:
   - export CHROME_BIN=chromium-browser
-  - npm run lint
-  - npm run test
+  - npm run ci

.prettierrc

@@ -1,47 +1,73 @@
+<a name="8.1.4">
+
+# [8.1.4 bugfix](2019-10-23)
+
+Fix for #580 - honour the special characters that user may have specified, and prevent runtime exception occuring
+
+Project folder structure converted over to follow Angular CLI way of libraries
+
+<a name="8.1.3">
+
+# [8.1.3 bugfix](2019-10-23)
+
+Fix for #590 - Problem if prefix last char is not a number
+
+<a name="8.1.2">
+
+# [8.1.2 placeholder customisation](2019-10-11)
+
+Placeholder can now be customised
+
 <a name="8.1.1">
 
-# [8.1.1 bugfix](2019-10-010)
+# [8.1.1 bugfix](2019-10-10)
+
 bugs fix
 
 <a name="8.1.0">
 
 # [8.1.0 separator update](2019-11-09)
-update separator
-<a name="8.1.0">
 
+update separator
 
 <a name="8.0.9">
 
-# [8.0.7 bugfix](2019-10-07)
+# [8.0.8 bugfix](2019-10-07)
+
 bugs fix [refs: #554, #580, #582]
 <a name="8.0.8">
 
 # [8.0.7 bugfix](2019-10-04)
+
 bugs fix [refs: #579, #576, #561]
 <a name="8.0.7">
 
 # [8.0.7 update date and time](2019-10-02)
+
 Update date and time masks [refs: #571, #567, #572, #564, #558, #573]
 
 <a name="8.0.4">
 
 # [8.0.4 bugfix](2019-09-09)
+
 minor bug fixes
 
 <a name="8.0.3">
 
 # [8.0.3 cursor](2019-09-04)
-minor bug fixes
 
+minor bug fixes
 
 <a name="7.9.9">
 
 # [7.9.9 cursor](2019-05-8)
+
 Issues fix
 
 <a name="7.9.2">
 
 # [7.9.1 cursor](2019-04-15)
+
 Bugs fix
 
 <a name="7.9.1">
@@ -201,25 +227,25 @@ You can pass into mask pattern with brackets
 
 <a name="6.4.14"></a>
 
-# [6.4.14 fixed '\*' pattern in maskExpression ](2018-10-05)
+# [6.4.14 fixed '\*' pattern in maskExpression](2018-10-05)
 
 Fixed pattern '\*'
 
 <a name="6.4.13"></a>
 
-# [6.4.13 selection of input value and deletion of it is fixed ](2018-10-05)
+# [6.4.13 selection of input value and deletion of it is fixed](2018-10-05)
 
 You can select and delete value.
 
 <a name="6.4.12"></a>
 
-# [6.4.12 pipe with mask expression and custom Pattern ](2018-04-10)
+# [6.4.12 pipe with mask expression and custom Pattern](2018-04-10)
 
 You can pass array of expression and custom Pattern to pipe
 
 <a name="6.3.11"></a>
 
-# [6.3.11 fixed mask visable ](2018-03-10)
+# [6.3.11 fixed mask visable](2018-03-10)
 
 Fixed when page is loaded the mask is visible
 

.travis.yml

@@ -1,32 +1,25 @@
-Contributing
-============
+# Contributing
 
-
-Issues
-======
+## Issues
 
 When submitting an issue, please include a reproducible case that we can actually run. Protractor has a test Angular application available at `http://www.protractortest.org/testapp` which you can use for the reproducible test case. If there's an error, please include the error text.
 
 Please format code and markup in your issue using [github markdown](https://help.github.com/articles/github-flavored-markdown).
 
+## Contributing to Source Code (Pull Requests)
 
-Contributing to Source Code (Pull Requests)
-===========================================
-
- * If your PR changes any behavior or fixes an issue, it should have an associated test.
- * New features should be general and as simple as possible.
- * Breaking changes should be avoided if possible.
- * All pull requests require review. No PR will be merged without a comment from a team member stating LGTM (Looks good to me).
+* If your PR changes any behavior or fixes an issue, it should have an associated test.
+* New features should be general and as simple as possible.
+* Breaking changes should be avoided if possible.
+* All pull requests require review. No PR will be merged without a comment from a team member stating LGTM (Looks good to me).
 
-Protractor specific rules
--------------------------
+## Protractor specific rules
 
- * JavaScript style should generally follow the [Google JS style guide](https://google.github.io/styleguide/javascriptguide.xml).
- * Document public methods with jsdoc.
- * Be consistent with the code around you!
+* JavaScript style should generally follow the [Google JS style guide](https://google.github.io/styleguide/javascriptguide.xml).
+* Document public methods with jsdoc.
+* Be consistent with the code around you!
 
-Commit Messages
----------------
+## Commit Messages
 
 Please write meaningful commit messages - they are used to generate the changelog, so the commit message should tell a user everything they need to know about a commit. Protractor follows AngularJS's [commit message format](https://docs.google.com/a/google.com/document/d/1QrDFcIiPjSLDn3EL15IJygNPiHORgU1_OOAqWjiDU5Y/edit#heading=h.z8a3t6ehl060).
 
@@ -39,8 +32,7 @@ In summary, this style is
 Where `<type>` is one of [feat, fix, docs, refactor, test, chore, deps] and
 `<scope>` is a quick descriptor of the location of the change, such as cli, clientSideScripts, element.
 
-Testing your changes
---------------------
+## Testing your changes
 
 When you submit a PR, tests will also be run on the Continuous Integration environment
 through Travis. If your tests fail on Travis, take a look at the logs.