Tags functionality when imported to postman question

[jord-nextlevelsoftware]

Hello all!

I have noticed that when importing the document.json into postman where I have custom tags in subfolder endpoints, it is giving some different behaviour to how it is displayed in Stoplight.

My folder structure is as follows:

• Folder1
  • Folder2

Folder 2 contains custom @tags called @tags Folder2Tag

When loading up the APIs in stoplight, this works fine and my Folder2Tag is now it's own folder containing all Folder2 endpoints that I applied the @tag to.

However, when exporting to postman (using "Tags" Folder Organization) I can see different behaviour, it is generating 2 folders with the same endpoints, essentially duplicating it:

• Folder2
• Folder2Tag

In stoplight, the Folder2 is omitted because I have custom tags applied, but in Postman it is including this as Folder2 is inside the tags object in the exported Open API spec.

This is the generated endpoint in the Open API spec that is exported from Stoplight:

"tags": [
      "Folder2Tag",
      "Folder2"
],

I guess my question for the above is, can we somehow stop the default tags generated (this this case Folder2) if we have applied custom tags on the endpoint? I

would expect that if I have applied a custom tag it should generate the tags like this for me only including the tags I have specified set in the sub folders endpoints:

"tags": [
      "Folder2Tag"
],

Thank you in advance!