Run Prettier for all supported file formats

.github/CONTRIBUTING.md

@@ -21,4 +21,4 @@ All submissions, including submissions by project members, require review. We
 use GitHub pull requests for this purpose. Consult [GitHub Help] for more
 information on using pull requests.
 
-[GitHub Help]: https://help.github.com/articles/about-pull-requests/
+[github help]: https://help.github.com/articles/about-pull-requests/

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

@@ -1,12 +1,14 @@
 ---
 name: "\U0001F4A1 Feature Request"
-about: Have a feature you'd like to see in the functions SDK? Request it through our
+about:
+  Have a feature you'd like to see in the functions SDK? Request it through our
   support channel.
 title: ''
 labels: ''
 assignees: ''
 ---
-<!-- DO NOT DELETE 
+
+<!-- DO NOT DELETE
 validate_template=false
 template_path=.github/ISSUE_TEMPLATE/---feature-request.md
 -->

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

@@ -1,12 +1,12 @@
 ---
-name: "⚠️ Report a Bug"
+name: '⚠️ Report a Bug'
 about: Think you found a bug in the SDK? Report it here.
 title: ''
 labels: ''
 assignees: ''
-
 ---
-<!-- DO NOT DELETE 
+
+<!-- DO NOT DELETE
 validate_template=true
 template_path=.github/ISSUE_TEMPLATE/---report-a-bug.md
 -->
@@ -21,11 +21,13 @@ template_path=.github/ISSUE_TEMPLATE/---report-a-bug.md
 be fixed in the latest versions. -->
 
 **node:**
+
 <!-- Run node --version and print the output here-->
 
 **firebase-functions:**
 
 **firebase-tools:**
+
 <!-- Run firebase --version and print the output here-->
 
 **firebase-admin:**
@@ -34,17 +36,14 @@ be fixed in the latest versions. -->
 
 <!-- Provide a minimal, complete, and verifiable example (http://stackoverflow.com/help/mcve) -->
 
-
 ### [REQUIRED] Steps to reproduce
 
 <!-- Provide the steps needed to reproduce the issue given the above test case. -->
 
-
 ### [REQUIRED] Expected behavior
 
 <!-- What is the expected behavior? -->
 
-
 ### [REQUIRED] Actual behavior
 
 <!-- Please copy and paste any error logs from https://console.firebase.google.com/project/_/functions/logs.

.github/PULL_REQUEST_TEMPLATE.md

@@ -5,8 +5,8 @@ and make note of the following:
 
 Run the linter and test suite
 ==============================
-Run `npm test` to make sure your changes compile properly and the tests all pass on your local machine. 
-We've hooked up this repo with continuous integration to double check those things for you. 
+Run `npm test` to make sure your changes compile properly and the tests all pass on your local machine.
+We've hooked up this repo with continuous integration to double check those things for you.
 
 Add tests (if applicable)
 ==============================
@@ -20,12 +20,11 @@ before sending PRs. We cannot accept code without this.
 
 -->
 
-
 ### Description
 
 <!-- Are you fixing a bug? Implementing a new feature? Make sure we have the context around your change.
 	 Link to other relevant issues or pull requests. -->
 
 ### Code sample
 
-<!-- Proposing an API change? Provide code samples showing how the API will be used. -->
+<!-- Proposing an API change? Provide code samples showing how the API will be used. -->

.prettierignore

@@ -0,0 +1,3 @@
+lib
+package.json
+spec/fixtures/credential/unparsable.key.json

integration_test/README.md

@@ -1,13 +1,13 @@
-How to Use
----------
+## How to Use
 
-***ATTENTION***: Running this test will wipe the contents of the Firebase project(s) you run it against. Make sure you use disposable Firebase project(s)!
+**_ATTENTION_**: Running this test will wipe the contents of the Firebase project(s) you run it against. Make sure you use disposable Firebase project(s)!
 
 Run the integration test as follows:
 
 ```bash
 ./run_tests.sh <project_id> [<project_id2>]
 ```
+
 If just one project_id is provided, the both the node6 and node8 tests will be run on that project, in series. If two project_ids are provided, the node6 tests will be run on the first project and the node8 tests will be run on the second one, in parallel.
 
 The tests run fully automatically, and will print the result on standard out. The integration test for HTTPS is that it properly kicks off other integration tests and returns a result. From there the other integration test suites will write their results back to the database, where you can check the detailed results if you'd like.

integration_test/functions/tsconfig.json

@@ -6,11 +6,7 @@
     "noImplicitAny": false,
     "outDir": "lib",
     "declaration": true,
-    "typeRoots": [
-      "node_modules/@types"
-    ]
+    "typeRoots": ["node_modules/@types"]
   },
-  "files": [
-    "src/index.ts"
-  ]
+  "files": ["src/index.ts"]
 }

package.json

@@ -25,8 +25,8 @@
     "build:pack": "rm -rf lib && npm install && tsc -p tsconfig.release.json && npm pack",
     "build:release": "npm install --production && npm install typescript firebase-admin && tsc -p tsconfig.release.json",
     "build": "tsc -p tsconfig.release.json",
-    "format": "prettier --check '**/*.ts'",
-    "format:fix": "prettier --write '**/*.ts'",
+    "format": "prettier --check '**/*.{json,md,ts,yml,yaml}'",
+    "format:fix": "prettier --write '**/*.{json,md,ts,yml,yaml}'",
     "lint": "tslint --config tslint.json --project tsconfig.json ",
     "lint:fix": "tslint --config tslint.json --fix --project tsconfig.json",
     "test": "mocha -r ts-node/register ./spec/index.spec.ts"

tsconfig.json

@@ -1,7 +1,7 @@
 {
   "compilerOptions": {
     "resolveJsonModule": true,
-    "sourceMap": true,
+    "sourceMap": true
   },
   "extends": "./tsconfig.release.json",
   "include": ["./src/**/*.ts", "./spec/**/*.ts"]