Merge remote-tracking branch 'upstream/master' into master

* upstream/master:
  chore: Release 2.0.0-rc.44 🔖
  feat: new extensions hook PropertyDetailsCell + wrap property name into span
  chore: add .vscode to .gitignore (Redocly#1416)
  chore: fix tests
  chore: Release 2.0.0-rc.43 🔖
  fix: fix broken observable after mobx upgrade (Redocly#1415)
  chore: Release 2.0.0-rc.42 🔖
  chore: update test snapshot (Redocly#1414)
  chore: upgrade to mobx@6 (Redocly#1412)
  fix: make schema layout more responsive on small screen (Redocly#1411)
  docs: unqualify mobx version for react usage (Redocly#1380)
  fix: make samples accessible by keyboard (Redocly#1401)
  docs: improvements to vendor extensions topic (Redocly#1386)
  fix: hide dropdown input on IE 11 (Redocly#1403)
  feat: Dockerfile compatible with OpenShift (Redocly#1407) (Redocly#1408)

.gitignore

@@ -36,3 +36,4 @@ cli/index.js
 stats.json
 yarn.lock
 .idea
+.vscode

CHANGELOG.md

@@ -1,3 +1,32 @@
+# [2.0.0-rc.44](https://github.com/Redocly/redoc/compare/v2.0.0-rc.43...v2.0.0-rc.44) (2020-10-16)
+
+
+### Features
+
+* new extensions hook PropertyDetailsCell + wrap property name into span ([0fae030](https://github.com/Redocly/redoc/commit/0fae03099645bd9d3795709175640583b08dfc3d))
+
+
+
+# [2.0.0-rc.43](https://github.com/Redocly/redoc/compare/v2.0.0-rc.42...v2.0.0-rc.43) (2020-10-13)
+
+
+### Bug Fixes
+
+* fix broken observable after mobx upgrade ([#1415](https://github.com/Redocly/redoc/issues/1415)) ([26c407b](https://github.com/Redocly/redoc/commit/26c407bd0f2bc1ec9881e0a3668e09e645fc0cc0))
+
+
+
+# [2.0.0-rc.42](https://github.com/Redocly/redoc/compare/v2.0.0-rc.41...v2.0.0-rc.42) (2020-10-13)
+
+
+### Bug Fixes
+
+* hide dropdown input on IE 11 ([#1403](https://github.com/Redocly/redoc/issues/1403)) ([6632d84](https://github.com/Redocly/redoc/commit/6632d844536532227cb92290f9fc2b6b2f913270))
+* make samples accessible by keyboard ([#1401](https://github.com/Redocly/redoc/issues/1401)) ([146b38c](https://github.com/Redocly/redoc/commit/146b38c9d0b926765d8e00dd37204c30bf3ac4e0))
+* make schema layout more responsive on small screen ([#1411](https://github.com/Redocly/redoc/issues/1411)) ([84ab95d](https://github.com/Redocly/redoc/commit/84ab95ddc7b5dc159098aecf82ad922ffd4a3093))
+
+
+
 # [2.0.0-rc.41](https://github.com/Redocly/redoc/compare/v2.0.0-rc.40...v2.0.0-rc.41) (2020-09-24)
 
 

README.md

@@ -138,7 +138,7 @@ For npm:
 
 Install peer dependencies required by ReDoc if you don't have them installed already:
 
-    npm i react react-dom mobx@^4.2.0 styled-components core-js
+    npm i react react-dom mobx styled-components core-js
 
 Import `RedocStandalone` component from 'redoc' module:
 

config/docker/Dockerfile

@@ -36,6 +36,18 @@ COPY demo/favicon.png /usr/share/nginx/html/
 COPY config/docker/nginx.conf /etc/nginx/
 COPY config/docker/docker-run.sh /usr/local/bin
 
+# Provide rights to the root group to write to nginx repositories (needed to run in OpenShift)
+RUN chgrp -R 0 /etc/nginx && \
+    chgrp -R 0 /usr/share/nginx/html && \
+    chgrp -R 0 /var/cache/nginx && \
+    chgrp -R 0 /var/log/nginx && \
+    chgrp -R 0 /var/run && \
+    chmod -R g+rwX /etc/nginx && \
+    chmod -R g+rwX /usr/share/nginx/html && \
+    chmod -R g+rwX /var/cache/nginx && \
+    chmod -R g+rwX /var/log/nginx && \
+    chmod -R g+rwX /var/run
+
 EXPOSE 80
 
 CMD ["sh", "/usr/local/bin/docker-run.sh"]

config/docker/README.md

@@ -2,6 +2,8 @@
 
 ## Usage
 
+### Docker
+
 Serve remote spec by URL:
 
     docker run -it --rm -p 80:80 \
@@ -12,13 +14,33 @@ Serve local file:
     docker run -it --rm -p 80:80 \
       -v $(pwd)/demo/swagger.yaml:/usr/share/nginx/html/swagger.yaml \
       -e SPEC_URL=swagger.yaml redocly/redoc
-      
+
 Serve local file and watch for updates:
 
     docker run -it --rm -p 80:80 \
       -v $(pwd)/demo/:/usr/share/nginx/html/swagger/ \
       -e SPEC_URL=swagger/swagger.yaml redocly/redoc
 
+### OpenShift
+
+To quote [OpenShift Container Platform-Specific Guidelines](https://docs.openshift.com/container-platform/3.11/creating_images/guidelines.html#openshift-specific-guidelines):
+
+> Support Arbitrary User IDs
+>
+> By default, OpenShift Container Platform runs containers using an arbitrarily assigned user ID. This provides additional security against processes escaping the container due to a container engine vulnerability and thereby achieving escalated permissions on the host node.
+>
+> For an image to support running as an arbitrary user, directories and files that may be written to by processes in the image should be owned by the root group and be read/writable by that group. Files to be executed should also have group execute permissions.
+
+To comply with those requirements the `Dockerfile` contains instructions to adapt the rights for the folders:
+
+- `/etc/nginx` because the `docker-run.sh` script modifies it at startup time
+- `/usr/share/nginx/html` because the `docker-run.sh` script modifies it at startup time
+- `/var/cache/nginx` because the Nginx process writes to it
+- `/var/log/nginx` because the Nginx process writes to it
+- `/var/run` because the Nginx process writes to it
+
+Another issue with OpenShift is that the default exposed port `80` cannot be used as it is restricted. So one needs to use another port like `8080` (using the `PORT` configuration as described below), and then to configure the `container spec` accordingly.
+
 ## Runtime configuration options
 
 - `PAGE_TITLE` (default `"ReDoc"`) - page title

docs/redoc-vendor-extensions.md

@@ -1,8 +1,34 @@
 # ReDoc vendor extensions
-ReDoc makes use of the following [vendor extensions](https://swagger.io/specification/#specificationExtensions)
 
-### Swagger Object vendor extensions
-Extend OpenAPI root [Swagger Object](https://swagger.io/specification/#oasObject)
+You can use the following [vendor extensions](https://swagger.io/specification/#specificationExtensions) with Redoc.
+
+- [Swagger Object](#swagger-object)
+	- [x-servers](#x-servers)
+	- [x-tagGroups](#x-taggroups)
+	- [Tag Group Object](#a-nametaggroupobjectatag-group-object)
+	- [x-ignoredHeaderParameters](#x-ignoredheaderparameters)
+- [Info Object](#info-object)
+	- [x-logo](#x-logo)
+	- [Logo Object](#a-namelogoobjectalogo-object)
+- [Tag Object](#tag-object)
+	- [x-traitTag](#x-traittag)
+	- [x-displayName](#x-displayname)
+- [Operation Object](#operation-object-vendor-extensions)
+	- [x-codeSamples](#x-codesamples)
+	- [Code Sample Object](#a-namecodesampleobjectacode-sample-object)
+- [Parameter Object](#parameter-object)
+	- [x-examples](#x-examples)
+- [Response Object vendor extensions](#response-object-vendor-extensions)
+	- [x-summary](#x-summary)
+- [Schema Object](#schema-object)
+	- [x-nullable](#x-nullable)
+	- [x-extendedDiscriminator](#x-extendeddiscriminator)
+	- [x-additionalPropertiesName](#x-additionalpropertiesname)
+	- [x-explicitMappingOnly](#x-explicitmappingonly)
+
+### Swagger Object
+Extends the OpenAPI root [OpenAPI Object](https://swagger.io/specification/#oasObject)
+
 #### x-servers
 Backported from OpenAPI 3.0 [`servers`](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#serverObject). Currently doesn't support templates.
 
@@ -12,9 +38,9 @@ Backported from OpenAPI 3.0 [`servers`](https://github.com/OAI/OpenAPI-Specifica
 | :------------- | :-----------: | :---------- |
 | x-tagGroups         | [ [Tag Group Object](#tagGroupObject) ] | A list of tag groups |
 
-###### Usage in Redoc
+###### How to use with Redoc
 `x-tagGroups` is used to group tags in the side menu.
-If you are going to use `x-tagGroups`, please make sure you **add all tags to a group**, since a tag that is not in a group, **will not be displayed** at all!
+Before you use `x-tagGroups`, make sure you **add all tags to a group**, since a tag that is not in a group, **will not be displayed** at all!
 
 #### <a name="tagGroupObject"></a>Tag Group Object
 Information about tags group
@@ -62,8 +88,8 @@ x-tagGroups:
 | x-ignoredHeaderParameters   | [ string ] | A list of ignored headers |
 
 
-###### Usage in Redoc
-`x-ignoredHeaderParameters` is used to specify header parameter names which are ignored by ReDoc
+###### How to use with Redoc
+Use `x-ignoredHeaderParameters` to specify header parameter names which are ignored by ReDoc.
 
 ###### x-ignoredHeaderParameters example
 ```yaml
@@ -77,19 +103,20 @@ x-ignoredHeaderParameters:
   - X-Test-Header
 ```
 
-### Info Object vendor extensions
-Extends OpenAPI [Info Object](http://swagger.io/specification/#infoObject)
+### Info Object
+Extends the OpenAPI [Info Object](http://swagger.io/specification/#infoObject)
 #### x-logo
 
 | Field Name     |	Type	       | Description |
 | :------------- | :-----------: | :---------- |
 | x-logo         | [Logo Object](#logoObject)  | The information about API logo |
 
-###### Usage in Redoc
-`x-logo` is used to specify API logo. The corresponding image are displayed just above side-menu.
+###### How to use with Redoc
+`x-logo` is used to specify API logo. The corresponding image is displayed just above the side-menu.
 
 #### <a name="logoObject"></a>Logo Object
 The information about API logo
+
 ###### Fixed fields
 | Field Name      |	Type	   | Description |
 | :-------------- | :------: | :---------- |
@@ -125,17 +152,16 @@ info:
     altText: "Petstore logo"
 ```
 
+### Tag Object
+Extends the OpenAPI [Tag Object](http://swagger.io/specification/#tagObject)
 
-
-### Tag Object vendor extensions
-Extends OpenAPI [Tag Object](http://swagger.io/specification/#tagObject)
 #### x-traitTag
 | Field Name     |	Type	  | Description |
 | :------------- | :------: | :---------- |
 | x-traitTag     | boolean  | In Swagger two operations can have multiple tags. This property distinguishes between tags that are used to group operations (default) from tags that are used to mark operation with certain trait (`true` value) |
 
-###### Usage in Redoc
-Tags that have `x-traitTag` set to `true` are listed in side-menu but don't have any subitems (operations). Tag `description` is rendered as well.
+###### How to use with Redoc
+Tags that have `x-traitTag` set to `true` are listed in the side-menu but don't have any subitems (operations). It also renders the `description` tag.
 This is useful for handling out common things like Pagination, Rate-Limits, etc.
 
 ###### x-traitTag example
@@ -161,17 +187,19 @@ x-traitTag: true
 | x-displayName  | string   | Defines the text that is used for this tag in the menu and in section headings |
 
 ### Operation Object vendor extensions
-Extends OpenAPI [Operation Object](http://swagger.io/specification/#operationObject)
+Extends the OpenAPI [Operation Object](http://swagger.io/specification/#operationObject)
+
 #### x-codeSamples
 | Field Name     |	Type	  | Description |
 | :------------- | :------: | :---------- |
 | x-codeSamples | [ [Code Sample Object](#codeSampleObject) ]  | A list of code samples associated with operation |
 
-###### Usage in ReDoc
-`x-codeSamples` are rendered on the right panel of ReDoc
+###### How to use with ReDoc
+`x-codeSamples` are rendered on the right panel in ReDoc.
 
 #### <a name="codeSampleObject"></a>Code Sample Object
 Operation code sample
+
 ###### Fixed fields
 | Field Name  |	Type	   | Description  |
 | :---------- | :------: | :----------- |
@@ -194,49 +222,51 @@ lang: JavaScript
 source: console.log('Hello World');
 ```
 
-### Parameter Object vendor extensions
-Extends OpenAPI [Parameter Object](http://swagger.io/specification/#parameterObject)
+### Parameter Object
+Extends the OpenAPI [Parameter Object](http://swagger.io/specification/#parameterObject)
+
 #### x-examples
 | Field Name     |  Type    | Description |
 | :------------- | :------: | :---------- |
 | x-examples | [Example Object](http://swagger.io/specification/#exampleObject)  | Object that contains examples for the request. Applies when `in` is `body` and mime-type is `application/json` |
 
-###### Usage in ReDoc
-`x-examples` are rendered in the JSON tab on the right panel of ReDoc.
+###### How to use with ReDoc
+`x-examples` are rendered in the JSON tab on the right panel in ReDoc.
 
 ### Response Object vendor extensions
-Extends OpenAPI [Response Object](https://swagger.io/specification/#responseObject)
+Extends the OpenAPI [Response Object](https://swagger.io/specification/#responseObject)
 
 #### x-summary
 | Field Name     |	Type	  | Description |
 | :------------- | :------: | :---------- |
 | x-summary      | string   | a short summary of the response |
 
-###### Usage in ReDoc
-If specified, `x-summary` is used as the response button text. Description is rendered under the button.
+###### How to use with ReDoc
+If specified, you can use `x-summary` as the response button text, with description rendered under the button.
+
+### Schema Object
+Extends the OpenAPI [Schema Object](http://swagger.io/specification/#schemaObject)
 
-### Schema Object vendor extensions
-Extends OpenAPI [Schema Object](http://swagger.io/specification/#schemaObject)
 #### x-nullable
 | Field Name     |	Type	  | Description |
 | :------------- | :------: | :---------- |
 | x-nullable | boolean | marks schema as a nullable |
 
-###### Usage in ReDoc
+###### How to use with ReDoc
 Schemas marked as `x-nullable` are marked in ReDoc with the label Nullable
 
 #### x-extendedDiscriminator
-**ATTENTION**: This is ReDoc-specific vendor extension. It won't be supported by other tools.
+**ATTENTION**: This is a ReDoc-specific vendor extension, and is not supported by other tools.
 
 | Field Name     |	Type	  | Description |
 | :------------- | :------: | :---------- |
 | x-extendedDiscriminator | string | specifies extended discriminator |
 
-###### Usage in ReDoc
+###### How to use with ReDoc
 ReDoc uses this vendor extension to solve name-clash issues with the standard `discriminator`.
 Value of this field specifies the field which will be used as a extended discriminator.
 ReDoc displays definition with selectpicker using which user can select value of the `x-extendedDiscriminator`-marked field.
-ReDoc displays the definition which is derived from the current (using `allOf`) and has `enum` with only one value which is the same as the selected value of the field specified as `x-extendedDiscriminator`.
+ReDoc displays the definition derived from the current (using `allOf`) and has `enum` with only one value which is the same as the selected value of the field specified as `x-extendedDiscriminator`.
 
 ###### x-extendedDiscriminator example
 
@@ -276,19 +306,18 @@ PayPalPayment:
           type: string
 ```
 
-In the example above the names of definitions (`PayPalPayment`) are named differently than
-names in the payload (`paypal`) which is not supported by default `discriminator`.
+In the example above, the names of definitions (`PayPalPayment`) are named differently than names in the payload (`paypal`) which is not supported by default `discriminator`.
 
 #### x-additionalPropertiesName
-**ATTENTION**: This is ReDoc-specific vendor extension. It won't be supported by other tools.
+**ATTENTION**: This is a ReDoc-specific vendor extension, and is not supported by other tools.
 
 Extends the `additionalProperties` property of the schema object.
 
 | Field Name     |	Type	  | Description |
 | :------------- | :------: | :---------- |
 | x-additionalPropertiesName | string | descriptive name of additional properties keys  |
 
-###### Usage in ReDoc
+###### How to use with ReDoc
 ReDoc uses this extension to display a more descriptive property name in objects with `additionalProperties` when viewing the property list with an `object`.
 
 ###### x-additionalPropertiesName example
@@ -308,18 +337,17 @@ Player:
 ```
 
 #### x-explicitMappingOnly
-**ATTENTION**: This is ReDoc-specific vendor extension. It won't be supported by other tools.
+**ATTENTION**: This is ReDoc-specific vendor extension, and is not supported by other tools.
 
 Extends the `discriminator` property of the schema object.
 
 | Field Name     |	Type	  | Description |
 | :------------- | :------: | :---------- |
 | x-explicitMappingOnly | boolean | limit the discriminator selectpicker to the explicit mappings only |
 
-###### Usage in ReDoc
+###### How to use with ReDoc
 ReDoc uses this extension to filter the `discriminator` mappings shown in the selectpicker.
-When set to `true`, the selectpicker will only list the the explicitly defined mappings. When `false`,
-the default behavior is kept, i.e. explicit and implicit mappings will be shown.
+When set to `true`, the selectpicker will only list the the explicitly defined mappings. When `false`, the default behavior is kept, i.e. explicit and implicit mappings will be shown.
 
 ###### x-explicitMappingOnly example
 
@@ -338,5 +366,4 @@ Pet:
       bee: "#/components/schemas/HoneyBee"
 ```
 
-Will show in the selectpicker only the items `cat` and `bee`, even though the `Dog` class inherits from
-the `Pet` class.
+Will show in the selectpicker only the items `cat` and `bee`, even though the `Dog` class inherits from the `Pet` class.