OpenAPI 3.0: $ref path string that includes a dot (name.name) doesn't import correctly.

ISSUE When importing an OpenAPI 3.0 .json file, with a $ref that points to a component path, if the path string contains a . (example: "$ref": "#/components/schemas/item.otherItem"), the path isn’t resolved correctly, and shows an error like the following in the field where the $ref was used:

"value": "reference #/components/schemas/item.otherItem not found in the api spec"

Replacing the .s with a _, allows the file to import correctly.

REPRODUCE:

1. Import the following file (with .s used) openapi3_works_not.json.zip
2. Open the example response No response was specfied for the request: com.nedap.healthcare.api.benchmark.Benchmark API.client Migration
3. Check response body, see following:

"benchmarkResults": [
  {
   "value": "reference #/components/schemas/benchmark.BenchmarkResult not found in the api spec"
  },

For comparison, try importing following file (where .s are replaced with _) openapi3_works.json.zip

[sciamano89]

Hi, just noticed that references that include dots cannot be clicked to “go to reference”. A fix would be awesome, thanks!!!

[abhijitkane]

@rasbreuknedap Thanks for the detailed report, and apologies for the delay here. I’ve opened up a PR for this fix - https://github.com/postmanlabs/openapi-to-postman/pull/54. We can make a release for this module soon, but this will only be updated in the next version of the Postman app. You can use this as a stand-alone module till then.