Added an ability to configure operationsSorter via ENV

Author: ryntric

docker/configurator/translator.js

@@ -50,6 +50,13 @@ const defaultBaseConfig = {
       type: "boolean",
       base: true,
     }
+  },
+  operationsSorter: {
+    value: "none",
+    schema: {
+      type: "string",
+      base: true
+    }
   }
 }
 

docker/configurator/variables.js

@@ -106,6 +106,10 @@ const standardVariables = {
   WITH_CREDENTIALS: {
     type: "boolean",
     name: "withCredentials",
+  },
+  OPERATIONS_SORTER: {
+    type: "string",
+    name: "operationsSorter",
   }
 }
 

docs/usage/configuration.md

@@ -139,7 +139,7 @@ Parameter name | Docker variable | Description
         <td>
             <a name="user-content-operationssorter"></a><code>operationsSorter</code>
         </td>
-        <td><em>Unavailable</em></td>
+        <td><code>OPERATIONS_SORTER</code></td>
         <td><code>Function=(a =&gt; a)</code>. Apply a sort to the operation
             list of each API. It can be 'alpha' (sort by paths
             alphanumerically), 'method' (sort by HTTP method) or a function (see

test/unit/docker/translator.js

@@ -147,6 +147,15 @@ describe("docker: env translator", function() {
       ))
     })
 
+    it("should generate operationsSorter configuration prop", function () {
+      const input = {
+        OPERATIONS_SORTER: "alpha"
+      }
+
+      expect(translator(input)).toEqual(dedent(`operationsSorter: true,`))
+
+    })
+
     it("should generate an object config", function () {
       const input = {
         SPEC: `{ swagger: "2.0" }`