make lint quiet.

Author: JAMES FUQIAN

.github/pull_request_template.md

@@ -0,0 +1,45 @@
+<!--
+You've got a Pull Request you want to submit? Awesome!
+This PR template is here to help ensure you're setup for success:
+  please fill it out to help ensure that your PR is complete and ready for approval.
+-->
+
+**JIRA Ticket:**
+[SOMEPROJECT-42](https://jira.cms.gov/browse/SOMEPROJECT-42)
+
+**User Story or Bug Summary:**
+
+<!-- Please copy-paste the brief user story or bug description that this PR is intended to address. -->
+
+### What Does This PR Do?
+
+<!--
+Add detailed description & discussion of changes here.
+The contents of this section should be used as your commit message (unless you merge the PR via a merge commit, of course).
+
+Please follow standard Git commit message guidelines:
+* First line should be a capitalized, short (50 chars or less) summary.
+* The rest of the message should be in standard Markdown format, wrapped to 72 characters.
+* Describe your changes in imperative mood, e.g. "make xyzzy do frotz" instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy to do frotz", as if you are giving orders to the codebase to change its behavior.
+* List all relevant Jira issue keys, one per line at the end of the message, per: <https://confluence.atlassian.com/jirasoftwarecloud/processing-issues-with-smart-commits-788960027.html>.
+
+Reference: <https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project>.
+-->
+
+### What Should Reviewers Watch For?
+
+<!--
+Add some items to the following list, or remove the entire section if it doesn't apply for some reason.
+
+Common items include:
+* Is this likely to address the goals expressed in the user story?
+* Are any additional documentation updates needed?
+* Are there any unhandled and/or untested edge cases you can think of?
+* Is user input properly sanitized & handled?
+* Does this make any backwards-incompatible changes that might break end user clients?
+* Can you find any bugs if you run the code locally and test it manually?
+-->
+
+If you're reviewing this PR, please check these things, in particular:
+
+- TODO

server/package.json

@@ -3,7 +3,7 @@
     "version": "0.0.0",
     "scripts": {
         "build": "./node_modules/.bin/ts-node build.ts",
-        "lint": "eslint --ext .ts --ext .js --ext .tsx .",
+        "lint": "eslint --fix --ext .ts --ext .tsx .",
         "start": "node -r module-alias/register ./dist --env=production",
         "start:debug": "node --inspect=0.0.0.0:9229 ./node_modules/.bin/ts-node -r tsconfig-paths/register ./src",
         "start:dev": "nodemon",
@@ -53,7 +53,8 @@
             "@typescript-eslint/no-explicit-any": 0,
             "@typescript-eslint/no-floating-promises": 0,
             "@typescript-eslint/no-unsafe-member-access": 0,
-            "@typescript-eslint/no-unsafe-assignment": 0
+            "@typescript-eslint/no-unsafe-assignment": 0,
+            "@typescript-eslint/no-unsafe-call": 0
         }
     },
     "eslintIgnore": [

server/src/__tests__/server_test.ts

@@ -15,8 +15,6 @@ const BB2_EOB_URL = `${BB2_BASE_URL}/v2/fhir/ExplanationOfBenefit/`;
 
 const BB2_PROFILE_URL = `${BB2_BASE_URL}/v2/connect/userinfo`;
 
-const BB2_AUTH_TOKEN_URL = `${BB2_BASE_URL}/v2/o/token/`;
-
 const eob = { status: 200, data: { resource: "EOB" } };
 
 const coverage = { status: 200, data: { resource: "Coverage" } };
@@ -42,8 +40,7 @@ const MOCK_AUTH_TOKEN = new AuthorizationToken(MOCK_AUTH_TOKEN_RESPONSE.data);
 let server: any;
 
 beforeAll(() => {
-    server = app.listen(Number(3003), () => {
-    });
+    server = app.listen(Number(3003));
   });
 
 afterAll(() => {
@@ -52,7 +49,7 @@ afterAll(() => {
 
 test("expect patient end point returns patient data.", async () => {
   // mock patient returned at deeper layer
-  jest.spyOn(reqs, 'get').mockImplementation((url, params, token) =>
+  jest.spyOn(reqs, 'get').mockImplementation((url) =>
     {
         if (url === BB2_PATIENT_URL) {
           return Promise.resolve(patient);
@@ -70,7 +67,7 @@ test("expect patient end point returns patient data.", async () => {
 
 test("expect profile end point returns profile data.", async () => {
   // mock profile returned at lower level get
-  jest.spyOn(reqs, 'get').mockImplementation((url, params, token) =>
+  jest.spyOn(reqs, 'get').mockImplementation((url) =>
     {
       if (url === BB2_PROFILE_URL) {
         return Promise.resolve(profile);
@@ -86,7 +83,7 @@ test("expect profile end point returns profile data.", async () => {
 
 test("expect coverage end point returns coverage data.", async () => {
     // mock coverage returned at deeper layer
-    jest.spyOn(reqs, 'get').mockImplementation((url, params, token) =>
+    jest.spyOn(reqs, 'get').mockImplementation((url) =>
         {
             if (url === BB2_COVERAGE_URL) {
             return Promise.resolve(coverage);
@@ -108,7 +105,7 @@ test("expect eob end point returns eob data.", async () => {
     loggedInUser.authToken = MOCK_AUTH_TOKEN;
 
     // mock eob returned at lower level get
-    jest.spyOn(reqs, 'get').mockImplementation((url, params, token) =>
+    jest.spyOn(reqs, 'get').mockImplementation((url) =>
         {
           if (url === BB2_EOB_URL) {
             return Promise.resolve(eob);
@@ -119,7 +116,6 @@ test("expect eob end point returns eob data.", async () => {
     );
 
     const response = await axios.get("http://localhost:3003/api/data/benefit-direct");
-    console.log(response);
     expect(response.status).toEqual(200);
     expect(response.data).toEqual(eob.data);
 });

server/src/pre-start/index.ts

@@ -2,7 +2,6 @@
  * Pre-start is where we want to place things that must run BEFORE the express server is started.
  * This is useful for environment variables, command-line arguments, and cron-jobs.
  */
-
 import path from 'path';
 import dotenv from 'dotenv';
 import commandLineArgs from 'command-line-args';