Postman is an API platform for building and using APIs. Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster.
Describe the bug
When attempting to import a RAML folder, I am getting an error that it cannot find an !include file, even though it appears the path to the file is correct. I am not sure if it is a Linux vs. Windows path delimiter issue that Postman is not properly handling on the Windows client or something else.
Steps to reproduce the behavior:
Click "Import" button at top of Postman window
Click on "Import Folder" tab
Click "Choose folders" button
Select the RAML folder created by unzipping downloaded RAML from Mulesoft for an API (also tried dragging the folder into the dialog, same results)
Get the following error:
Error while importing RAML 0.8: while reading file Error: Unable to find file
c:/Users/username/Downloads/product-asset-data-api-1.0.1-raml/schemas/outbound/products.json in uploaded data in
"C:\Users\username\Downloads\product-asset-data-api-1.0.1-raml/api.raml", line 25, column 27: - productsResponse: !include schemas/outbound/product ... ^
But the file referenced exists at the expected path:
dir C:\Users\username\Downloads\product-asset-data-api-1.0.1-raml\schemas\outbound\products.json
Directory: C:\Users\username\Downloads\product-asset-data-api-1.0.1-raml\schemas\outbound
Mode LastWriteTime Length Name
---- ------------- ------ ----
-------- 12/4/2018 3:35 PM 81275 products.json
Expected behavior
It would import the RAML information with all its goodness
App information:
App Type: Native Windows App
Postman Version: Version 7.17.0
OS: win32 10.0.18363 / x64
The top level of the RAML folder contains api.raml which has the following line in it (among others, but this is the line relevant to the error:
Describe the bug When attempting to import a RAML folder, I am getting an error that it cannot find an !include file, even though it appears the path to the file is correct. I am not sure if it is a Linux vs. Windows path delimiter issue that Postman is not properly handling on the Windows client or something else.
Steps to reproduce the behavior:
But the file referenced exists at the expected path:
Expected behavior It would import the RAML information with all its goodness
App information:
The top level of the RAML folder contains
api.raml
which has the following line in it (among others, but this is the line relevant to the error: