orderOfOperations is not working as expected (apideck/[email protected])

[Tanmay2711]

Hi Team,
I am using below configuration -

portman-config.json
"orderOfOperations":[
"POST::/*",
"GET::/*",
"PATCH::/*",
"DELETE::/*"
],

and schema.json

Path - /provider/domain/v1/entity
Operations -
GET
POST

Path - /provider/domain/v1/entity/{id}
Operations -
DELETE
GET
PATCH

Note: All operations have unique operationIds specified.

and postman-config.json
{
"folderStrategy": "Paths",
"requestParametersResolution": "Example"
}

command -
npx portman -l schema.json -b http://localhost -o postman-collection.json -c portman-config.json --postmanConfigFile postman-config.json

Expected behavior -
for path /provider/domain/v1/entity it should generate requests in order - POST, GET
for path /provider/domain/v1/entity/{id}, it should generate requests in order - GET, PATCH and DELETE

Actual behavior -
for path /provider/domain/v1/entity it generates requests in order - POST, GET (Working as expected)
for path /provider/domain/v1/entity/{id}, it keeps the same order - DELETE, GET, PATCH (Not working as expected)

[JaredCE]

I Agree, there is something funky with order of operations:

portman-config.json

{
  "version": 1.0,
  "globals": {
    "orderOfOperations": [
      "POST::/batch/{organisationId}",
      "PATCH::/{paymentCodeId}",
      "GET::/{paymentCodeId}",
      "POST::/filter/{organisationId}",
      "PATCH::/allocate/{organisationId}",
      "PATCH::/{paymentCodeId}/{organisationId}",
      "POST::/verify",
      "PATCH::/used",
      "POST::/create/{organisationId}",
      "DELETE::/{paymentCodeId}/{organisationId}"
    ]
  }
}

results in a postman collection generated:

{
  "_": {
    "postman_id": "fc88856f-4aff-4c01-abee-a50700e42fe8"
  },
  "item": [
    {
          "_": {
            "portman_operation": "POST::/batch/:organisationId"
          }
    },
    {
          "_": {
            "portman_operation": "PATCH::/:paymentCodeId/:organisationId"
          }
     },
     {
         "_": {
            "portman_operation": "PATCH::/:paymentCodeId"
          },
      },
      {
          "_": {
            "portman_operation": "GET::/:paymentCodeId"
          }
      }   
  ]
}

Somehow that "portman_operation": "PATCH::/:paymentCodeId/:organisationId" operation is getting added in very early compared to where i would expect it, based on the provided orderOfOperations

[vampyar]

I'm created same issues #621, maybe its not working totally, because it this test it checked only call function

portman/src/application/CollectionWriter.test.ts

Line 75 in 2c1946b

describe('orderCollectionRequests', () => {