Support ES6

.eslintrc

@@ -1,7 +1,7 @@
 {
-  "extends": ["eslint:recommended", "eslint-config-hapi"],
+  "extends": ["eslint:recommended", "plugin:@hapi/recommended"],
   "parserOptions": {
-    "ecmaVersion": 2018,
+    "ecmaVersion": 2020,
     "sourceType": "module"
   },
   "env": {

.vscode/launch.json

@@ -1,18 +1,18 @@
 {
-    // Use IntelliSense to learn about possible attributes.
-    // Hover to view descriptions of existing attributes.
-    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
-    "version": "0.2.0",
-    "configurations": [
-        {
-            "type": "node",
-            "request": "launch",
-            "name": "Tape Current File",
-            "program": "${workspaceFolder}/node_modules/tape/bin/tape",
-            "args": [
-                "${file}"
-            ],
-            "console": "internalConsole"
-        }
-    ]
-}
+  // Use IntelliSense to learn about possible attributes.
+  // Hover to view descriptions of existing attributes.
+  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
+  "version": "0.2.0",
+  "configurations": [
+    {
+      "type": "node",
+      "request": "launch",
+      "name": "Tape Current File",
+      "program": "${workspaceFolder}/node_modules/tape/bin/tape",
+      "args": [
+        "${file}"
+      ],
+      "console": "internalConsole"
+    }
+  ]
+}

CHANGELOG.md

@@ -7,7 +7,7 @@
 - Don't set undefined parameters on request in `routeExt` (#180)
 - Update enjoi and @hapi/joi to Joi 17 (#176)
 
-### 2.0.1 
+### 2.0.1
 
 - Removed left over console.log file
 - Fixed `unknown` being used on all joi schemas as opposed to just objects
@@ -43,7 +43,8 @@
 
 ### 1.2.0
 
-- Vendor extensions are now stripped from the API docs end point (option `docs.stripExtensions`).
+- Vendor extensions are now stripped from the API docs end point (option
+  `docs.stripExtensions`).
 - Bumped to Enjoi 4.x.
 
 ### 1.1.0
@@ -56,11 +57,13 @@
 
 ### 1.0.4
 
-- Resolves https://github.com/krakenjs/hapi-openapi/issues/123, fixing array format support in parameters.
+- Resolves https://github.com/krakenjs/hapi-openapi/issues/123, fixing array
+  format support in parameters.
 
 ### 1.0.3
 
-- Resolves https://github.com/krakenjs/hapi-openapi/issues/125, correcting `date-time` format.
+- Resolves https://github.com/krakenjs/hapi-openapi/issues/125, correcting
+  `date-time` format.
 
 ### 1.0.2
 
@@ -105,7 +108,8 @@
 
 ### 3.3.1
 
-- Fixed https://github.com/krakenjs/swaggerize-hapi/issues/72 - allow single item arrays.
+- Fixed https://github.com/krakenjs/swaggerize-hapi/issues/72 - allow single
+  item arrays.
 
 ### 3.3.0
 
@@ -127,7 +131,9 @@
 
 - [BREAKING] Migrated to Hapi 17 and Node 8.
 - [BREAKING] Severed from `swaggerize-routes` - this module is now standalone.
-- [BREAKING] `server.plugins.swagger.api` is now `server.plugins.swagger.getApi()`.
-- [BREAKING] `handlers` object doesn't namespace http methods using `$` anymore. Assumption is verb is last in object path.
+- [BREAKING] `server.plugins.swagger.api` is now
+  `server.plugins.swagger.getApi()`.
+- [BREAKING] `handlers` object doesn't namespace http methods using `$` anymore.
+  Assumption is verb is last in object path.
 - [BREAKING] Currently does not work with the `swaggerize-generator`.
 - Routes will specify what they allow based on api spec.

CODE_OF_CONDUCT.md

@@ -2,45 +2,73 @@
 
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of
+experience, nationality, personal appearance, race, religion, or sexual identity
+and orientation.
 
 ## Our Standards
 
-Examples of behavior that contributes to creating a positive environment include:
+Examples of behavior that contributes to creating a positive environment
+include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
 
 ## Our Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
 
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening,
+offensive, or harmful.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. The project team
+will review and investigate all complaints, and will respond in a way that it
+deems appropriate to the circumstances. The project team is obligated to
+maintain confidentiality with regard to the reporter of an incident. Further
+details of specific enforcement policies may be posted separately.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
 
 [homepage]: http://contributor-covenant.org
 [version]: http://contributor-covenant.org/version/1/4/