build: format all files

All files are now formatted using the ng-dev tools via prettier.

.github/ISSUE_TEMPLATE/1-bug-report.md

@@ -2,6 +2,7 @@
 name: "\U0001F41E Bug report"
 about: Report a bug in Angular CLI
 ---
+
 <!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅
 
 Oh hi there! 😄
@@ -11,10 +12,10 @@ Existing issues often contain information about workarounds, resolution, or prog
 
 🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->
 
-
 # 🐞 Bug report
 
 ### Command (mark with an `x`)
+
 <!-- Can you pin-point the command or commands that are effected by this bug? -->
 <!-- ✍️edit: -->
 
@@ -34,26 +35,24 @@ Existing issues often contain information about workarounds, resolution, or prog
 - [ ] version
 - [ ] doc
 
-
 ### Is this a regression?
 
 <!-- Did this behavior use to work in the previous version? -->
 <!-- ✍️--> Yes, the previous version in which this bug was not present was: ....
 
-
 ### Description
 
 <!-- ✍️--> A clear and concise description of the problem...
 
-
 ## 🔬 Minimal Reproduction
+
 <!--
 Simple steps to reproduce this bug.
 
 Please include: commands run (including args), packages added, related code changes.
 
-If reproduction steps are not enough for reproduction of your issue, please create a minimal GitHub repository with the reproduction of the issue. 
-A good way to make a minimal reproduction is to create a new app via `ng new repro-app` and add the minimum possible code to show the problem. 
+If reproduction steps are not enough for reproduction of your issue, please create a minimal GitHub repository with the reproduction of the issue.
+A good way to make a minimal reproduction is to create a new app via `ng new repro-app` and add the minimum possible code to show the problem.
 Share the link to the repo below along with step-by-step instructions to reproduce the problem, as well as expected and actual behavior.
 
 Issues that don't have enough info and can't be reproduced will be closed.
@@ -62,21 +61,23 @@ You can read more about issue submission guidelines here: https://github.com/ang
 -->
 
 ## 🔥 Exception or Error
+
 <pre><code>
 <!-- If the issue is accompanied by an exception or an error, please share it below: -->
 <!-- ✍️-->
 
 </code></pre>
 
-
 ## 🌍 Your Environment
+
 <pre><code>
 <!-- run `ng version` and paste output below -->
 <!-- ✍️-->
 
 </code></pre>
 
 **Anything else relevant?**
+
 <!-- ✍️Is this a browser specific issue? If so, please specify the browser and version. -->
 
 <!-- ✍️Do any of these matter: operating system, IDE, package manager, HTTP server, ...? If so, please mention it below. -->

.github/ISSUE_TEMPLATE/2-feature-request.md

@@ -1,8 +1,8 @@
 ---
 name: "\U0001F680 Feature request"
 about: Suggest a feature for Angular CLI
-
 ---
+
 <!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅
 
 Oh hi there! 😄
@@ -12,13 +12,13 @@ Existing issues often contain information about workarounds, resolution, or prog
 
 🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->
 
-
 # 🚀 Feature request
 
-
 ### Command (mark with an `x`)
+
 <!-- Can you pin-point the command or commands that are relevant for this feature request? -->
 <!-- ✍️edit: -->
+
 - [ ] new
 - [ ] build
 - [ ] serve
@@ -36,12 +36,13 @@ Existing issues often contain information about workarounds, resolution, or prog
 - [ ] doc
 
 ### Description
-<!-- ✍️--> A clear and concise description of the problem or missing capability...
 
+<!-- ✍️--> A clear and concise description of the problem or missing capability...
 
 ### Describe the solution you'd like
-<!-- ✍️--> If you have a solution in mind, please describe it.
 
+<!-- ✍️--> If you have a solution in mind, please describe it.
 
 ### Describe alternatives you've considered
+
 <!-- ✍️--> Have you considered any alternative solutions or workarounds?

.github/ISSUE_TEMPLATE/3-docs-bug.md

@@ -1,7 +1,6 @@
 ---
-name: "📚 Docs or angular.io issue report"
+name: '📚 Docs or angular.io issue report'
 about: Report an issue in Angular's documentation or angular.io application
-
 ---
 
 🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑

.github/ISSUE_TEMPLATE/4-security-issue-disclosure.md

@@ -1,7 +1,6 @@
 ---
 name: ⚠️ Security issue disclosure
 about: Report a security issue in Angular Framework, Material, or CLI
-
 ---
 
 🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑

.github/ISSUE_TEMPLATE/5-support-request.md

@@ -1,14 +1,13 @@
 ---
-name: "❓ Support request"
+name: '❓ Support request'
 about: Questions and requests for support
-
 ---
 
 🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑
 
 Please do not file questions or support requests on the GitHub issues tracker.
 
-You can get your questions answered using other communication channels. Please see: 
+You can get your questions answered using other communication channels. Please see:
 https://github.com/angular/angular-cli/blob/master/CONTRIBUTING.md#question
 
 Thank you!

.github/ISSUE_TEMPLATE/6-angular-framework.md

@@ -1,7 +1,6 @@
 ---
-name: "⚡Angular Framework"
+name: '⚡Angular Framework'
 about: Issues and feature requests for Angular Framework
-
 ---
 
 🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑

.github/ISSUE_TEMPLATE/7-angular-material.md

@@ -1,7 +1,6 @@
 ---
 name: "\U0001F48E Angular Material"
 about: Issues and feature requests for Angular Material
-
 ---
 
 🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑

.github/SAVED_REPLIES.md

@@ -4,52 +4,52 @@ The following are canned responses that the Angular CLI team should use to close
 
 Since GitHub currently doesn't allow us to have a repository-wide or organization-wide list of [saved replies](https://help.github.com/articles/working-with-saved-replies/), these replies need to be maintained by individual team members. Since the responses can be modified in the future, all responses are versioned to simplify the process of keeping the responses up to date.
 
-
 ## Angular CLI: Already Fixed (v1)
+
 ```
 Thanks for reporting this issue. Luckily, it has already been fixed in one of the recent releases. Please update to the most recent version to resolve the problem.
 
 If the problem persists in your application after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior. You can use `ng new repro-app` to create a new project where you reproduce the problem.
 ```
 
-
 ## Angular CLI: Don't Understand (v1)
+
 ```
 I'm sorry, but we don't understand the problem you are reporting.
 
 If the problem persists, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior. You can use `ng new repro-app` to create a new project where you reproduce the problem.
 ```
 
-
 ## Angular CLI: Duplicate (v1.1)
+
 ```
 Thanks for reporting this issue. However, this issue is a duplicate of #<ISSUE_NUMBER>. Please subscribe to that issue for future updates.
 ```
 
-
 ## Angular CLI: Insufficient Information Provided (v1)
+
 ```
 Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out [our submission guidelines](https://github.com/angular/angular-cli/blob/master/CONTRIBUTING.md#-submitting-an-issue) to understand why we can't act on issues that are lacking important information.
 
 If the problem persists, please file a new issue and ensure you provide all of the required information when filling out the issue template.
 ```
 
-
 ## Angular CLI: NPM install issue (v1)
+
 ```
 This seems like a problem with your node/npm and not with Angular CLI.
 
 Please have a look at the [fixing npm permissions page](https://docs.npmjs.com/getting-started/fixing-npm-permissions), [common errors page](https://docs.npmjs.com/troubleshooting/common-errors), [npm issue tracker](https://github.com/npm/npm/issues), or open a new issue if the problem you are experiencing isn't known.
 ```
 
-
 ## Angular CLI: Issue Outside of Angular CLI (v1.1)
+
 ```
 I'm sorry, but this issue is not caused by Angular CLI. Please contact the author(s) of the <PROJECT NAME> project or file an issue on their issue tracker.
 ```
 
-
 ## Angular CLI: Non-reproducible (v1)
+
 ```
 I'm sorry, but we can't reproduce the problem following the instructions you provided.
 Remember that we have a large number of issues to resolve, and have only a limited amount of time to reproduce your issue.
@@ -60,24 +60,24 @@ If the problem persists, please open a new issue following [our submission guide
 A good way to make a minimal repro is to create a new app via `ng new repro-app` and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
 ```
 
-
 ## Angular CLI: Obsolete (v1)
+
 ```
 Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.
 
 If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.
 ```
 
-
 ## Angular CLI: Support Request (v1)
+
 ```
 Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on [StackOverflow](http://stackoverflow.com/) using tag `angular-cli`.
 
 If you are wondering why we don't resolve support issues via the issue tracker, please [check out this explanation](https://github.com/angular/angular-cli/blob/master/CONTRIBUTING.md#-got-a-question-or-problem).
 ```
 
-
 ## Angular CLI: Static Analysis errors (v1)
+
 ```
 Hello, errors like `Error encountered resolving symbol values statically` mean that there has been some problem in statically analyzing your app.
 
@@ -93,6 +93,7 @@ In that case, please open an issue in https://github.com/angular/angular.
 ```
 
 ## Angular CLI: Lockfiles (v1)
+
 ```
 I'd like to remind everyone that **you only have reproducible installs if you use a lockfile**. Both [NPM v5+](https://docs.npmjs.com/files/package-locks) and [Yarn](https://yarnpkg.com/lang/en/docs/yarn-lock/) support lockfiles. If your CI works one day but not the next and you did not change your code or `package.json`, it is likely because one of your dependencies had a bad release and you did not have a lockfile.
 

.github/angular-robot.yml

@@ -7,11 +7,11 @@ merge:
     # set to true to disable
     disabled: false
     # the name of the status
-    context: "ci/angular: merge status"
+    context: 'ci/angular: merge status'
     # text to show when all checks pass
-    successText: "All checks passed!"
+    successText: 'All checks passed!'
     # text to show when some checks are failing
-    failureText: "The following checks are failing:"
+    failureText: 'The following checks are failing:'
 
   # comment that will be added to a PR when there is a conflict, leave empty or set to false to disable
   mergeConflictComment: >-
@@ -20,7 +20,7 @@ merge:
     Please help to unblock it by resolving these conflicts. Thanks!
 
   # label to monitor
-  mergeLabel: "action: merge"
+  mergeLabel: 'action: merge'
 
   # list of checks that will determine if the merge label can be added
   checks:
@@ -30,28 +30,28 @@ merge:
     requireReviews: true
     # list of labels that a PR needs to have, checked with a regexp (e.g. "target:" will work for the label "target: major")
     requiredLabels:
-      - "target: *"
-      - "cla: yes"
+      - 'target: *'
+      - 'cla: yes'
 
     # list of labels that a PR shouldn't have, checked after the required labels with a regexp
     forbiddenLabels:
-      - "action: cleanup"
-      - "action: review"
-      - "PR state: blocked"
-      - "cla: no"
+      - 'action: cleanup'
+      - 'action: review'
+      - 'PR state: blocked'
+      - 'cla: no'
 
     # list of PR statuses that need to be successful
     requiredStatuses:
-      - "ci/circleci: build"
-      - "ci/circleci: setup"
-      - "ci/circleci: lint"
-      - "ci/circleci: validate"
-      - "ci/circleci: test"
-      - "ci/circleci: e2e-cli-win"
-      - "ci/circleci: e2e-cli"
-      - "ci/circleci: test-browsers"
-      - "ci/angular: size"
-      - "cla/google"
+      - 'ci/circleci: build'
+      - 'ci/circleci: setup'
+      - 'ci/circleci: lint'
+      - 'ci/circleci: validate'
+      - 'ci/circleci: test'
+      - 'ci/circleci: e2e-cli-win'
+      - 'ci/circleci: e2e-cli'
+      - 'ci/circleci: test-browsers'
+      - 'ci/angular: size'
+      - 'cla/google'
 
   # the comment that will be added when the merge label is added despite failing checks, leave empty or set to false to disable
   # {{MERGE_LABEL}} will be replaced by the value of the mergeLabel option
@@ -78,30 +78,24 @@ triage:
   defaultMilestone: 12,
   # arrays of labels that determine if an issue has been triaged by the caretaker
   l1TriageLabels:
-    -
-      - "comp: *"
+    - - 'comp: *'
   # arrays of labels that determine if an issue has been fully triaged
   l2TriageLabels:
-    -
-      - "type: bug/fix"
-      - "severity*"
-      - "freq*"
-      - "comp: *"
-    -
-      - "type: feature"
-      - "comp: *"
-    -
-      - "type: refactor"
-      - "comp: *"
-    -
-      - "type: RFC / Discussion / question"
-      - "comp: *"
-    -
-      - "type: docs"
-      - "comp: *"
+    - - 'type: bug/fix'
+      - 'severity*'
+      - 'freq*'
+      - 'comp: *'
+    - - 'type: feature'
+      - 'comp: *'
+    - - 'type: refactor'
+      - 'comp: *'
+    - - 'type: RFC / Discussion / question'
+      - 'comp: *'
+    - - 'type: docs'
+      - 'comp: *'
 
 # Size checking
 size:
-  circleCiStatusName: "ci/circleci: e2e-cli"
+  circleCiStatusName: 'ci/circleci: e2e-cli'
   maxSizeIncrease: 10000
   comment: false