VIIgit · VIIgit · Aug 9, 2019 · Apr 10, 2019 · Apr 10, 2019 · Apr 13, 2019
diff --git a/.babelrc b/.babelrc
@@ -1,51 +1,46 @@
 {
   "presets": [
-    "es2015",
-    "react",
-    "stage-0"
+    [
+      "@babel/env",
+      {
+        "targets": {
+          "browsers": [
+            /* benefit of C/S/FF/Edge only? */
+            "> 1%",
+            "last 2 versions",
+            "Firefox ESR",
+            "not dead",
+          ]
+        },
+        "useBuiltIns": "entry",
+        "corejs": "2"
+      }
+    ],
+    "@babel/preset-react"
   ],
   "plugins": [
-    "transform-runtime",
-    "babel-plugin-transform-es2015-constants",
+    ["@babel/plugin-transform-runtime", {
+      "corejs": "2"
+    }],
+    "@babel/plugin-proposal-class-properties",
+    "@babel/plugin-proposal-optional-chaining",
     ["transform-react-remove-prop-types", {
       "additionalLibraries": ["react-immutable-proptypes"]
     }],
     [
-      "module-alias",
-      [
-        {
-          "expose": "root",
-          "src": "."
-        },
-        {
-          "expose": "components",
-          "src": "src/core/components"
-        },
-        {
-          "expose": "containers",
-          "src": "src/core/containers"
-        },
-        {
-          "expose": "core",
-          "src": "src/core"
-        },
-        {
-          "expose": "plugins",
-          "src": "src/plugins"
-        },
-        {
-          "expose": "img",
-          "src": "src/img"
-        },
-        {
-          "expose": "corePlugins",
-          "src": "src/core/plugins"
-        },
-        {
-          "expose": "less",
-          "src": "src/less"
+      "babel-plugin-module-resolver",
+      {
+        "alias": {
+          "root": ".",
+          "components": "./src/core/components",
+          "containers": "./src/core/containers",
+          "core": "./src/core",
+          "plugins": "./src/plugins",
+          "img": "./src/img",
+          "corePlugins": "./src/core/plugins",
+          "less": "./src/less",
         }
-      ]
+      }
     ]
   ]
 }
diff --git a/.github/lock.yml b/.github/lock.yml
@@ -0,0 +1,15 @@
+daysUntilLock: 365
+skipCreatedBefore: 2017-03-29 # initial release of Swagger UI 3.0.0
+exemptLabels: []
+lockLabel: "locked-by: lock-bot"
+setLockReason: false
+only: issues
+lockComment: false
+# lockComment: |
+#   Locking due to inactivity.
+
+#   This is done to avoid resurrecting old issues and bumping long threads with new, possibly unrelated content.
+
+#   If you think you're experiencing something similar to what you've found here: please [open a new issue](https://github.com/swagger-api/swagger-ui/issues/new/choose), follow the template, and reference this issue in your report.
+
+#   Thanks!
diff --git a/.prettierrc.yaml b/.prettierrc.yaml
@@ -0,0 +1,5 @@
+semi: false
+trailingComma: es5
+endOfLine: lf
+requirePragma: true
+insertPragma: true
diff --git a/Dockerfile b/Dockerfile
@@ -20,7 +20,11 @@ COPY ./dist/* /usr/share/nginx/html/
 COPY ./docker/run.sh /usr/share/nginx/
 COPY ./docker/configurator /usr/share/nginx/configurator
 
-RUN chmod +x /usr/share/nginx/run.sh
+RUN chmod +x /usr/share/nginx/run.sh && \
+    chmod -R a+rw /usr/share/nginx && \
+    chmod -R a+rw /etc/nginx && \
+    chmod -R a+rw /var && \
+    chmod -R a+rw /var/run
 
 EXPOSE 8080
 

diff --git a/README.md b/README.md
@@ -1,6 +1,7 @@
 # <img src="https://raw.githubusercontent.com/swagger-api/swagger.io/wordpress/images/assets/SWU-logo-clr.png" height="80">
 
 [![NPM version](https://badge.fury.io/js/swagger-ui.svg)](http://badge.fury.io/js/swagger-ui)
+[![Build Status](https://jenkins.swagger.io/view/OSS%20-%20JavaScript/job/oss-swagger-ui-master/badge/icon?subject=jenkins%20build)](https://jenkins.swagger.io/view/OSS%20-%20JavaScript/job/oss-swagger-ui-master/)
 
 **👉🏼 Want to score an easy open-source contribution?** Check out our [Good first issue](https://github.com/swagger-api/swagger-ui/issues?q=is%3Aissue+is%3Aopen+label%3A%22Good+first+issue%22) label.
 

diff --git a/SECURITY.md b/SECURITY.md
@@ -0,0 +1,21 @@
+# Security Policy
+
+If you believe you've found an exploitable security issue in Swagger UI,
+**please don't create a public issue**. 
+
+
+## Supported versions
+
+This is the list of versions of `swagger-ui` which are
+currently being supported with security updates.
+
+| Version  | Supported          | Notes                  |
+| -------- | ------------------ | ---------------------- |
+| 3.x      | :white_check_mark: |                        |
+| 2.x      | :x:                | End-of-life as of 2017 |
+
+## Reporting a vulnerability
+
+To report a vulnerability please send an email with the details to [[email protected]](mailto:[email protected]).
+
+We'll acknowledge receipt of your report ASAP, and set expectations on how we plan to handle it.
diff --git a/dist/swagger-ui-bundle.js b/dist/swagger-ui-bundle.js
diff --git a/dist/swagger-ui-bundle.js.map b/dist/swagger-ui-bundle.js.map
diff --git a/dist/swagger-ui-standalone-preset.js b/dist/swagger-ui-standalone-preset.js
diff --git a/dist/swagger-ui-standalone-preset.js.map b/dist/swagger-ui-standalone-preset.js.map
diff --git a/dist/swagger-ui.css b/dist/swagger-ui.css
diff --git a/dist/swagger-ui.css.map b/dist/swagger-ui.css.map
diff --git a/dist/swagger-ui.js b/dist/swagger-ui.js
diff --git a/dist/swagger-ui.js.map b/dist/swagger-ui.js.map
diff --git a/docs/README.md b/docs/README.md
@@ -1,5 +1,5 @@
-# Swagger-UI
+# Swagger UI
 
-Welcome to the Swagger-UI documentation!
+Welcome to the Swagger UI documentation!
 
 A table of contents can be found at `SUMMARY.md`.
diff --git a/docs/book.json b/docs/book.json
@@ -1,3 +1,3 @@
 {
-  "title": "Swagger-UI"
+  "title": "Swagger UI"
 }
diff --git a/docs/customization/custom-layout.md b/docs/customization/custom-layout.md
@@ -1,8 +1,8 @@
 # Creating a custom layout
 
-**Layouts** are a special type of component that Swagger-UI uses as the root component for the entire application. You can define custom layouts in order to have high-level control over what ends up on the page.
+**Layouts** are a special type of component that Swagger UI uses as the root component for the entire application. You can define custom layouts in order to have high-level control over what ends up on the page.
 
-By default, Swagger-UI uses `BaseLayout`, which is built into the application. You can specify a different layout to be used by passing the layout's name as the `layout` parameter to Swagger-UI. Be sure to provide your custom layout as a component to Swagger-UI.
+By default, Swagger UI uses `BaseLayout`, which is built into the application. You can specify a different layout to be used by passing the layout's name as the `layout` parameter to Swagger UI. Be sure to provide your custom layout as a component to Swagger UI.
 
 <br>
 

diff --git a/docs/customization/overview.md b/docs/customization/overview.md
@@ -2,7 +2,7 @@
 
 ### Prior art
 
-Swagger-UI leans heavily on concepts and patterns found in React and Redux.
+Swagger UI leans heavily on concepts and patterns found in React and Redux.
 
 If you aren't already familiar, here's some suggested reading:
 
@@ -17,7 +17,7 @@ In the following documentation, we won't take the time to define the fundamental
 
 ### The System
 
-The _system_ is the heart of the Swagger-UI application. At runtime, it's a JavaScript object that holds many things:
+The _system_ is the heart of the Swagger UI application. At runtime, it's a JavaScript object that holds many things:
 
 - React components
 - Bound Redux actions and reducers
@@ -27,11 +27,11 @@ The _system_ is the heart of the Swagger-UI application. At runtime, it's a Java
 - References to the React and Immutable.js libraries (`system.React`, `system.Im`)
 - User-defined helper functions
 
-The system is built up when Swagger-UI is called by iterating through ("compiling") each plugin that Swagger-UI has been given, through the `presets` and `plugins` configuration options.
+The system is built up when Swagger UI is called by iterating through ("compiling") each plugin that Swagger UI has been given, through the `presets` and `plugins` configuration options.
 
 ### Presets
 
-Presets are arrays of plugins, which are provided to Swagger-UI through the `presets` configuration option. All plugins within presets are compiled before any plugins provided via the `plugins` configuration option. Consider the following example:
+Presets are arrays of plugins, which are provided to Swagger UI through the `presets` configuration option. All plugins within presets are compiled before any plugins provided via the `plugins` configuration option. Consider the following example:
 
 ```javascript
 const MyPreset = [FirstPlugin, SecondPlugin, ThirdPlugin]
@@ -43,7 +43,7 @@ SwaggerUI({
 })
 ```
 
-By default, Swagger-UI includes the internal `ApisPreset`, which contains a set of plugins that provide baseline functionality for Swagger-UI. If you specify your own `presets` option, you need to add the ApisPreset manually, like so:
+By default, Swagger UI includes the internal `ApisPreset`, which contains a set of plugins that provide baseline functionality for Swagger UI. If you specify your own `presets` option, you need to add the ApisPreset manually, like so:
 
 ```javascript
 SwaggerUI({
@@ -54,15 +54,15 @@ SwaggerUI({
 })
 ```
 
-The need to provide the `apis` preset when adding other presets is an artifact of Swagger-UI's original design, and will likely be removed in the next major version.
+The need to provide the `apis` preset when adding other presets is an artifact of Swagger UI's original design, and will likely be removed in the next major version.
 
 ### getComponent
 
 `getComponent` is a helper function injected into every container component, which is used to get references to components provided by the plugin system.
 
 All components should be loaded through `getComponent`, since it allows other plugins to modify the component. It is preferred over a conventional `import` statement.
 
-Container components in Swagger-UI can be loaded by passing `true` as the second argument to `getComponent`, like so:
+Container components in Swagger UI can be loaded by passing `true` as the second argument to `getComponent`, like so:
 
 ```javascript
 getComponent("ContainerComponentName", true)

diff --git a/docs/customization/plug-points.md b/docs/customization/plug-points.md
@@ -1,16 +1,16 @@
 # Plug points
 
-Swagger-UI exposes most of its internal logic through the plugin system.
+Swagger UI exposes most of its internal logic through the plugin system.
 
 Often, it is beneficial to override the core internals to achieve custom behavior.
 
 ### Note: Semantic Versioning
 
-Swagger-UI's internal APIs are _not_ part of our public contract, which means that they can change without the major version changing.
+Swagger UI's internal APIs are _not_ part of our public contract, which means that they can change without the major version changing.
 
-If your custom plugins wrap, extend, override, or consume any internal core APIs, we recommend specifying a specific minor version of Swagger-UI to use in your application, because they will _not_ change between patch versions.
+If your custom plugins wrap, extend, override, or consume any internal core APIs, we recommend specifying a specific minor version of Swagger UI to use in your application, because they will _not_ change between patch versions.
 
-If you're installing Swagger-UI via NPM, for example, you can do this by using a tilde:
+If you're installing Swagger UI via NPM, for example, you can do this by using a tilde:
 
 ```js
 {

diff --git a/docs/customization/plugin-api.md b/docs/customization/plugin-api.md
@@ -1,14 +1,14 @@
 # Plugins
 
-A plugin is a function that returns an object - more specifically, the object may contain functions and components that augment and modify Swagger-UI's functionality.
+A plugin is a function that returns an object - more specifically, the object may contain functions and components that augment and modify Swagger UI's functionality.
 
 ### Note: Semantic Versioning 
 
-Swagger-UI's internal APIs are _not_ part of our public contract, which means that they can change without the major version changing.
+Swagger UI's internal APIs are _not_ part of our public contract, which means that they can change without the major version changing.
 
-If your custom plugins wrap, extend, override, or consume any internal core APIs, we recommend specifying a specific minor version of Swagger-UI to use in your application, because they will _not_ change between patch versions.
+If your custom plugins wrap, extend, override, or consume any internal core APIs, we recommend specifying a specific minor version of Swagger UI to use in your application, because they will _not_ change between patch versions.
 
-If you're installing Swagger-UI via NPM, for example, you can do this by using a tilde:
+If you're installing Swagger UI via NPM, for example, you can do this by using a tilde:
 
 ```js
 {
@@ -96,7 +96,7 @@ Once an action has been defined, you can use it anywhere that you can get a syst
 system.exampleActions.updateFavoriteColor("blue")
 ```
 
-The Action interface enables the creation of new Redux action creators within a piece of state in the Swagger-UI system.
+The Action interface enables the creation of new Redux action creators within a piece of state in the Swagger UI system.
 
 This action creator function will be exposed to container components as `exampleActions.updateFavoriteColor`. When this action creator is called, the return value (which should be a [Flux Standard Action](https://github.com/acdlite/flux-standard-action)) will be passed to the `example` reducer, which we'll define in the next section.
 
@@ -225,7 +225,7 @@ A Wrap Action's first argument is `oriAction`, which is the action being wrapped
 This mechanism is useful for conditionally overriding built-in behaviors, or listening to actions.
 
 ```javascript
-// FYI: in an actual Swagger-UI, `updateSpec` is already defined in the core code
+// FYI: in an actual Swagger UI, `updateSpec` is already defined in the core code
 // it's just here for clarity on what's behind the scenes
 const MySpecPlugin = function(system) {
   return {
@@ -251,9 +251,9 @@ const MyWrapActionPlugin = function(system) {
       spec: {
         wrapActions: {
           updateSpec: (oriAction, system) => (str) => {
-            // here, you can hand the value to some function that exists outside of Swagger-UI
+            // here, you can hand the value to some function that exists outside of Swagger UI
             console.log("Here is my API definition", str)
-            return oriAction(str) // don't forget! otherwise, Swagger-UI won't update
+            return oriAction(str) // don't forget! otherwise, Swagger UI won't update
           }
         }
       }
@@ -273,7 +273,7 @@ This interface is useful for controlling what data flows into components. We use
 ```javascript
 import { createSelector } from 'reselect'
 
-// FYI: in an actual Swagger-UI, the `url` spec selector is already defined
+// FYI: in an actual Swagger UI, the `url` spec selector is already defined
 // it's just here for clarity on what's behind the scenes
 const MySpecPlugin = function(system) {
   return {

diff --git a/docs/development/scripts.md b/docs/development/scripts.md
@@ -6,11 +6,11 @@ Any of the scripts below can be run by typing `npm run <script name>` in the pro
 Script name | Description
 --- | ---
 `dev` | Spawn a hot-reloading dev server on port 3200.
-`deps-check` | Generate a size and licensing report on Swagger-UI's dependencies.
+`deps-check` | Generate a size and licensing report on Swagger UI's dependencies.
 `lint` | Report ESLint style errors and warnings.
 `lint-errors` | Report ESLint style errors, without warnings.
 `lint-fix` | Attempt to fix style errors automatically.
-`watch` | Rebuild the core files in `/dist` when the source code changes. Useful for `npm link` with Swagger-Editor.
+`watch` | Rebuild the core files in `/dist` when the source code changes. Useful for `npm link` with Swagger Editor.
 
 ### Building
 Script name | Description
@@ -19,12 +19,12 @@ Script name | Description
 `build-bundle` | Build `swagger-ui-bundle.js` only.
 `build-core` | Build `swagger-ui.(js\|css)` only.
 `build-standalone` | Build `swagger-ui-standalone-preset.js` only.
+`build-stylesheets` | Build `swagger-ui.css` only.
 
 ### Testing
 Script name | Description
 --- | ---
 `test` | Run unit tests in Node and run ESLint in errors-only mode.
 `just-test` | Run unit tests in the browser with Karma.
 `just-test-in-node` | Run unit tests in Node.
-`just-check-coverage` | Generate a code coverage report with NYC.
 `e2e` | Run end-to-end tests (requires JDK and Selenium).
diff --git a/docs/development/setting-up.md b/docs/development/setting-up.md
@@ -1,6 +1,6 @@
 # Setting up a dev environment
 
-Swagger-UI includes a development server that provides hot module reloading and unminified stack traces, for easier development.
+Swagger UI includes a development server that provides hot module reloading and unminified stack traces, for easier development.
 
 ### Prerequisites
 
@@ -20,5 +20,5 @@ Swagger-UI includes a development server that provides hot module reloading and
 
 ## Bonus points
 
-- Swagger-UI includes an ESLint rule definition. If you use a graphical editor, consider installing an ESLint plugin, which will point out syntax and style errors for you as you code.
+- Swagger UI includes an ESLint rule definition. If you use a graphical editor, consider installing an ESLint plugin, which will point out syntax and style errors for you as you code.
   - The linter runs as part of the PR test sequence, so don't think you can get away with not paying attention to it!